| Platform SDK: Windows Installer |
Event Logging
Event logging in Windows NT/Windows 2000 provides a standard,
centralized way for applications (and the operating system) to record important
software and hardware events. The event-logging service stores events from
various sources in a single collection called an event log. Windows
NT/Windows 2000 also supplies Event Viewer for viewing the logs, and a
programming interface for examining the logs. For more information, see
The installer also writes entries into the Event Log. These record events such as following:
- Success or failure of the installation, removal, or repair of a product.
- Errors that occur during product configuration.
- Detection of corrupted configuration data.
If a large amount of information is written the Event Log file can become full and the installer displays a message, "The Application log file is full."
Note there is no built-in Event Log on Windows 95 or Windows 98. On these systems, the installer logs the same event information into a file in the %temp% folder called Msievent.log. For more information, see Checking for the Installation of Features, Components, or Files.
The installer may write the following entries in the event log. Starting with Windows Installer version 2.0, all event log messages have a unique event ID.
| Event ID | Message | Remarks |
|---|---|---|
| 1001 | Detection of product '%1', feature '%2' failed during request for component '%3' | A warning message. For details, see Searching For a Broken Feature or Component. |
| 1002 | Unexpected or missing value (name: '%1', value: '%2') in key '%3' | Error message that there was an unexpected or missing value. |
| 1003 | Unexpected or missing subkey '%1' in key '%2' | Error message that there was an unexpected or missing subkey. |
| 1004 | Detection of product '%1', feature '%2', component '%3'
failed
Note: Beginning with Windows Installer version 2.0, this message is: Detection of product '%1', feature '%2', component '%3' failed. The resource '%4' does not exist. |
A warning message. See also Searching For a Broken Feature or Component. |
| 1005 | Install operation initiated a reboot | Informational message that the installation initiated a reboot of the system. |
| 1006 | Verification of the digital signature for cabinet '%1' cannot be performed. WinVerifyTrust is not available on the machine. | Only available on Windows Installer version 2.0 or later. Warning message. A cabinet was authored in the MsiDigitalSignature table to have a WinVerifyTrust check performed. This action could not be performed because the computer does not have the proper cryptography DLLs installed. |
| 1007 | The installation of %1 is not permitted by software restriction policy. The Windows Installer only allows execution of unrestricted items. The authorization level returned by software restriction policy was %2. | Only available on Windows Installer version 2.0 or later. An error message indicating that the administrator has configured software restriction policy to disallow this install. |
| 1008 | The installation of %1 is not permitted due to an error in software restriction policy processing. The object cannot be trusted. | Only available on Windows Installer version 2.0 or later. An error message indicating that there were problems attempting to verify the package according to software restriction policy. |
| 1012 | This version of Windows does not support deploying 64-bit packages. The script '%1' is for a 64-bit package. | Error message indicating that scripts for 64-bit packages can only be executed on a 64-bit computer. |
| 1013 | {Unhandled exception report} | Error message for an unhandled exception, this is the report. |
| 1014 | Windows Installer proxy information not registered correctly | Error message that proxy information was not registered correctly. |
| 1015 | Failed to connect to server. Error: %d | Informational message that the installation failed to connect to server. |
| 1016 | Detection of product '%1', feature '%2', component '%3' failed. The resource '%4' in a run-from-source component could not be located because no valid and accessible source could be found. | Warning message. For more information, see Searching for a Broken Feature or Component. |
| 1017 | User SID had changed from '%1' to '%2' but the managed app and the user data keys cannot be updated. Error = '%3'. | Error message indicating that an error occurred while attempting to update the user's registration after the user's SID changed. |
| 11707 | Product [2] � Installation operation completed successfully | Informational message that the installation of the product was successful. |
| 11708 | Product [2] � Installation operation failed | Error message that the installation of the product failed. |
| 11728 | Product [2] -- Configuration completed successfully. | Informational message that configuration of the product was successful. |
'
)
|
|