JDK-6781427 : Add the ability to collect MSI error numbers, not just "1603"
  • Type: Enhancement
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10,6-pool
  • Priority: P2
  • Status: Closed
  • Resolution: Won't Fix
  • OS: windows,windows_xp
  • CPU: x86
  • Submitted: 2008-12-05
  • Updated: 2022-01-27
  • Resolved: 2013-09-12
Related Reports
Duplicate :  
JDK-6975241 - MSI internal error code should be passed to the wrapper and pinged in the Main Error evar
Relates :  
JDK-6964353 - enhance logging and add pings for CheckPendingFileRenameOperations error during JRE install
Description
Add the ability to collect MSI error numbers, not just "1603"

The Glossary in the SiteCatalyst: JRE Errors - hourly Dashboard for Global Account report says:
1603 = cab file unavailable, error applying transform, or some other fatal error.

I know that an Errors 1606, 1722, 25099, and 26011 in Windows Installer could all cause 1603, but don't know which one of the errors it was.
Comments
This enhancement is coverd by introduction of MainError and ExtendedError pings.
12-09-2013
EVALUATION 6964353 will ping errors 25025 and 25026. Code now exists to ping other values.
14-02-2011