JDK-7047810 : Installer Unpack code that could cause MSI error 1603 should include 260XX errors in ping data
  • Type: Enhancement
  • Component: install
  • Sub-Component: install
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2011-05-24
  • Updated: 2022-01-27
  • Resolved: 2016-01-20
Related Reports
Relates :  
JDK-6964353 - enhance logging and add pings for CheckPendingFileRenameOperations error during JRE install
Relates :  
JDK-6975241 - MSI internal error code should be passed to the wrapper and pinged in the Main Error evar
Description
Errors 25025 and 25026 not only are displayed to the user but when MSI Error 1603 is returned, they are included in evar 24 (main error) in the ping (See CR 6964353).

We should add errors 26011, 26022, 26033, 26044, 26055, 26066, and 26077 to evar 24 (main error) in the ping when those cause MSI Error 1603 to be returned.
Comments
Enhancement, 2+ major releases, P4. WNF.
20-01-2016
MSI Compliance project/Redesign.
11-06-2013
SUGGESTED FIX Add call to SetMSIStatus(nError, uExtendedError); from ExecUnpackCmd() in install\make\installerdll\installerdll\src\installer\RegInstall.cpp
24-05-2011