Click to Rate and Give Feedback
MSDN
MSDN Library
Windows Installer
System Policy
Machine Policies
 Debug
Debug

If this per-machine system policy is set to "1", the installer writes common debugging messages to the debugger using the OutputDebugString function. If this value is set to "2", the installer writes all valid debugging messages to the debugger using the OutputDebugString function. This policy is for debugging purposes only and may not be supported in future versions of Windows Installer.

Windows Installer only writes command lines into the log file if the third (0x04) bit is set in the value of the Debug policy. Therefore, to display command lines in the log, set the Debug policy value to 7. This does not display properties associated with an Edit Control having the Password Control Attribute. This will make properties set on the command line visible in the log even if the property is included in the MsiHiddenProperties property. For more information, see Preventing Confidential Information from Being Written into the Log File.

Registry Key

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\
     Windows\Installer

Data Type

REG_DWORD


Send comments about this topic to Microsoft

Build date: 6/5/2008

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Sample WindowsInstallerTroubleshootingViaPolicy.reg Use and Contents      Robert Flaming - MSFT   |   Edit   |  

When you need to troubleshoot a failing install, it is often useful to use the policy hive rather than the command line to catch things like repairs and multi-pacakge installs.

To use the code below

1) Start Notepad

2) copy and paste the snippit below into the notepad file

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmupx"
"Debug"=dword:00000007


3) File -> save

4) use file name WindowsInstallerTroubleshootingViaPolicy.reg

5) be sure to change the file type to All files so that notepad doesn't attend .txt

6) hit save

7) at the command prompt (make sure it's elevated if you are running Vista or greater)

  1. net stop msiserver
  2. run the file WindowsInstallerTroubleshootingViaPolicy.reg which will add the values below to your registry
  3. net start msiserver

8) rerun your scenario

9) look in the %temp% directory for files that start with the letters "MSI". Depending on the nuances of your scenario, these files could be in

    • user temp
    • administrator temp
    • Windows temp


10) consult your favorite reference for reading logs such as

Robert Flaming
Windows Installer Program Manager
Team Blog: http://blogs.msdn.com/windows_installer_team
Own Blog: http://blogs.msdn.com/rflaming

All postings are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker