Windows Installer logging

Version 1

    Verified Product Versions

    AppSense Management Center 8.7AppSense Management Center 8.6AppSense Management Center 8.5AppSense Management Center 8.4AppSense Management Center 8.3AppSense Environment Manager 10.0AppSense Environment Manager 8.6AppSense Environment Manager 8.5AppSense Environment Manager 8.4AppSense Environment Manager 8.3AppSense Environment Manager 10.1AppSense Performance Manager 10.0AppSense Performance Manager 8.3AppSense Performance Manager 10.1AppSense Management Center 10.0AppSense Management Center 10.1AppSense Application Manager 10.0AppSense Application Manager 8.9AppSense Application Manager 8.8AppSense Application Manager 8.7AppSense Application Manager 8.6AppSense Application Manager 8.5AppSense Application Manager 8.4AppSense Application Manager 8.3AppSense Application Manager 10.1AppSense DataNow 3.6AppSense DataNow 3.5AppSense DataNow 3.0AppSense DataNow 2.0AppSense DataNow 4.0AppSense DataNow 4.1AppSense Insight 10.0AppSense Insight 1.3AppSense Insight 1.4AppSense Insight 10.1


    If you find that a software installation is failing then you may want to enable Windows Installer logging to look for errors. This applies to any MSI/MSP installation, not just AppSense products.

    This logging is enabled by adding keys and values to the registry. After the entries have been added and enabled, you can retry the problem installation and Windows Installer will track the progress and post it to the Temp folder. The new log's file name is random. However, the first letters are "Msi" and the file name has a ".log: extension.


    To enable Windows Installer logging, open the registry by using Regedit.exe, and then create the following key and value:

    Key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
    Reg_SZ: Logging
    Value: voicewarmupx

    The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 1.1:

    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
    x - Extra debugging information.

    "*" - Wildcard: Log all information except the v and the x option. To include the v and the x option, specify "/l*vx".

    NOTE: This change should be used only for troubleshooting and should not be left on because it will have adverse effects on system performance and disk space. Each time that you use the Add or Remove Programs item in Control Panel, a new Msi*.log file is created.