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).
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).
- duplicates
-
JDK-6781427 Add the ability to collect MSI error numbers, not just "1603"
-
- Closed
-
- relates to
-
JDK-7048823 Code cleanup: Errors 27000 and 27010 were for Kernel can be removed from JRE MSI
-
- Closed
-
-
JDK-7047810 Installer Unpack code that could cause MSI error 1603 should include 260XX errors in ping data
-
- Closed
-