|Q104807: HOWTO: Logging an MSI Installation|
|AdminStudio 10.x, AdminStudio 9.x, InstallShield 2009 Premier, InstallShield 2009 Professional, InstallShield 2010 Express, InstallShield 2010 Premier, InstallShield 2010 Professional, InstallShield 2011 Express, InstallShield 2011 Premier, InstallShield 2011 Professional, InstallShield 2012 Express, InstallShield 2012 Premier, InstallShield 2012 Professional, InstallShield 2012 Spring Express, InstallShield 2012 Spring Premier, InstallShield 2012 Spring Professional|
|Basic MSI, InstallScript MSI|
To create a log file that records the progress of the installation, you need to execute your MSI package at the command line using the
To log the execution of an MSI package you need to include /l along with one or more of the flags from the following table, in addition to any other command-line parameters you may be using. A path that indicates where the log file should go is also necessary.
Here is an example of a command line that logs everything verbosely. This provides the maximum amount of information obtainable via logging.
Other modifiers can be used in conjunction with the /l switch. They are listed in the following table.
Here are a few more examples of command lines that log installations.
Keep track of the sequence in which actions start and stop during uninstallation:
Log just the errors:
Log events that are minuter in scope than the actions and keep track of out of memory and disk space errors:
Get a list of all of the properties and their values at the end of the installation, but append it to package.log instead of overwriting it:
Logging through setup.exe
If you have built a single compressed setup.exe and do not have direct access to the MSI file, you can use setup.exe's
Pass the logging-specific switches and parameters as an argument to
Keep the following in mind when doing this:
To duplicate the functionality of the example above using setup.exe, the following command line can be used:
Logging in Windows Installer 4.0 and Windows Vista
Windows Installer 4.0 allows MSI logging to occur on a project-wide basis without having to use the command line or configure log parameters through the registry. To learn more about this option, review the InstallShield Help article entitled Specifying Whether Windows Installer Installations Should Be Logged.
For more information on logging, see these Microsoft articles:
|Q105237: HOWTO: Logging An InstallScript MSI Project|
|Last Modified Date: 09-13-2012ID: Q104807|