Enable MSI Installer Logging
Created: 05 Jun 2008 | 2 comments
I just learned that you can enable MSI logging so that if your installer fails with an error you can see where the MSI failed.
To enable MSI loggging:
- Open Regedit.
- Go to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer.
- Create a new Reg_SZ value named "Logging" with the value "voicewarmup".
While "voicewarmup" is easy to remember, it actually signifies all of the different options that you want to enable.
Here is the complete list of options:
| v | Verbose output |
| o | Out-of-disk-space messages |
| i | Status messages |
| c | Initial UI parameters |
| e | All error messages |
| w | Non-fatal warnings |
| a | Start up of actions |
| r | Action-specific records |
| m | Out-of-memory or fatal exit information |
| u | User requests |
| p | Terminal properties |
| + | Append to existing file |
| ! | Flush each line to the log |
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments 2 Comments • Jump to latest comment
You can now enable logging on a per package basis on Vista(MSI 4.0 or above). Just use the new property MsiLogging within the desired MSI package.
There is also the DisableLoggingFromPackage policy to override this if Administrators wish. The MsiLogFileLocation property holds the log file location and name of the file for easier locating.
Other methods to generate logs can be found in this below link..
http://juice.altiris.com/tip/2560/trobleshooting-a...
http://juice.altiris.com/article/1358/troubleshoot...
Hope this helps.
Cheers'
Vijay
Microsoft MVP [Setup-Deploy]
Weblog: www.msigeek.com
Here is the Microsoft MSDN support url for MSI cmd line options. http://msdn.microsoft.com/en-us/library/aa367988%2...
Condor man, you are correct and your suggestion will create a System policy for MSI logging. In some scenarios such as Active Directory or resillency the AD policy may be the only way to get a log. However keep in mind that highly verbose logging can have a system performance hit.
All of these logging options can be accomplished if you send the same command line to the MSI file directly.
E.g. msiexec /i "MyInstaller.msi" /L*v mylog.txt
Would you like to reply?
Login or Register to post your comment.