InstallShield 2019
Project • This information applies to the following project types:
| • | Advanced UI |
| • | Suite/Advanced UI |
Edition • The Advanced UI project type is available in the Professional edition of InstallShield. The Suite/Advanced UI project type is available in the Premier edition of InstallShield. For information about the differences between these two project types, see Advanced UI Projects vs. Suite/Advanced UI Projects.
When you are configuring the settings for a package in an Advanced UI or Suite/Advanced UI project, you can specify whether you want the package to generate a log file if the Advanced UI or Suite/Advanced UI installation is launched from the command line with the /log command-line parameter. Depending on the type of package, you can also configure one or two other settings to specify information such as which log options you want the Advanced UI or Suite/Advanced UI installation to pass to the package when the log file is being created.
Note that if a package does not have support for logging, it is recommended that you leave logging support disabled for that package.
Enabling Package Logging Support
To enable logging support for a package in an Advanced UI or Suite/Advanced UI installation:
| 1. | Open the Advanced UI or Suite/Advanced UI project that contains the package for which you want to enable logging. |
| 2. | In the View List under Organization, click Packages. |
| 3. | In the Packages explorer, select the package that you want to configure. |
| 4. | On the Common tab, in the Enable Logging Support setting, select Yes. |
| 5. | For an .msi or .msp package, configure the following optional subsettings as needed: |
| • | Log File—Specify a name for the log file. Do not include a path for the file; the Advanced UI or Suite/Advanced UI /log command-line parameter lets end users specify the directory for the package log files. |
If you leave this setting blank, the name of the log file that the installation creates is PackageGUID.log, where PackageGUID is the GUID that is assigned to the package in the Package GUID setting in the Packages view.
| • | Log Options—Specify the Windows Installer log /L flags that you want the package to use when generating the log file. For example, to generate a log file that logs everything verbosely, enter the following in this setting: |
*v
For additional valid flags, see the /L description.
If you leave this setting blank, the asterisk (*) and v flags are used to generate the log file.
For an .exe package, configure the following subsetting:
| • | Logging Command Line—Specify the command line that the Advanced UI or Suite/Advanced UI installation should pass to the .exe package to enable the logging. Include any appropriate supported flags. If the .exe package that you are configuring supports it, include a path that references the Advanced UI or Suite/Advanced UI property ISLogDir, enclosed within square brackets, in place of the path to the directory where the log file should be created. |
For example, to generate a log file that logs everything verbosely for an .msi package that is run by a Setup.exe file that InstallShield built, enter the following command line:
/v"/l*v \"[ISLogDir]FileName.log\""
The Advanced UI or Suite/Advanced UI installation replaces [ISLogDir] with the path to the folder that will contain the log file. The Advanced UI or Suite/Advanced UI /log command-line parameter lets end users specify the path to the directory for the package log files.
Generating Package Log Files While Running an Advanced UI or Suite/Advanced UI Installation
To create a package log file, run the Advanced UI or Suite/Advanced UI installation from the command line with the /log parameter. The /log parameter lets you generate a log file for each package in the Advanced UI or Suite/Advanced UI installation for which logging is enabled.
To generate package log files in a particular folder, pass the folder path with the /log parameter to the Advanced UI or Suite/Advanced UI Setup.exe file. You can optionally separate the /log parameter and the path with a colon. For example, both of the following command lines generate a log file in the PathToLogFiles folder:
Setup.exe /log"C:\PathToLogFiles"
Setup.exe /log:"C:\PathToLogFiles"
Note that the path to the log file location must already exist.
To generate package log files in the %TEMP% directory, leave out the path. For example:
Setup.exe /log
The Advanced UI or Suite/Advanced UI property ISLogDir stores the path to the directory that contains the package log files.
Tip • You can also use the logging system policy or the MsiLogging property to generate log files for Windows Installer–based packages in an Advanced UI or Suite/Advanced UI installation.
See Also
Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation
InstallShield 2019 Help LibraryApril 2019 |
Copyright Information | Flexera |