JDK-6975241 : MSI internal error code should be passed to the wrapper and pinged in the Main Error evar
- Type: Bug
- Component: install
- Sub-Component: install
- Affected Version: 6-pool
- Priority: P2
- Status: Closed
- Resolution: Duplicate
- OS: windows
- CPU: x86
- Submitted: 2010-08-06
- Updated: 2022-01-27
- Resolved: 2011-07-28
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 |
|---|
8Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
There is a difference in MSI execution between the error that is displayed to a user, and the return code that the msiexec.exe process returns to our wrapper. For example a user may see error 1723, but what the MSI returns, and what we ping, is 1603. In order to be able to correlate specific errors that users are reporting to determine impact, we need both the return code and the error code from MSI. A mechanism should be added that passes the MSI error code (e.g. 1723) back to the installer wrapper. The wrapper should then send the MSI error in the install complete ping using the new Main Error evar (evar-24).