InstallShield 2015
Project: This information applies to InstallScript projects.
Setup.exe may produce error messages if it cannot start properly. In most cases, you will encounter these messages when a severe error occurs. Rarely will your end users see these messages.
You can capture these return values when you call the CreateProcess API to launch Setup.exe, or use a batch file to launch Setup.exe.
When you get an error message, it appears in a message box. Every error message has a number. These are InstallScript system error messages, and there is no way to suppress them in your script. The following table describes each of these error messages:
|
Error/Return Value |
Description |
|
3010 |
The installation required a restart but the installation is not initiating the restart. In this case, the installation completed with BATCH_INSTALL set to a non-zero value, but the System function was not called. Note that Setup.exe returns this value only if the installation was successful and was not cancelled (that is, the installation did not end via the abort keyword). Otherwise, the appropriate error value or ISERR_SETUP_CANCELED is returned. The constant for this return value is ERROR_SUCCESS_REBOOT_REQUIRED. |
|
1641 |
This return value occurs if the installation itself is restarting the machine because the System function was called—typically as a result of the SdFinishReboot function calling System internally. Note that Setup.exe returns this value only if the installation was successful and was not cancelled (that is, the installation did not end via the abort keyword). Otherwise, the appropriate error value or ISERR_SETUP_CANCELED is returned. The constant for this return value is ERROR_SUCCESS_REBOOT_INITIATED. |
|
0 |
The installation exited with the exit keyword. |
|
0x80042000 |
The installation exited with the abort keyword because the end user canceled the installation. The constant for this return value is ISERR_SETUP_CANCELED. |
|
0x80040708 |
Unable to create required engine components. Check whether you have appropriate privileges to create COM components. Note: This error message may include an additional error number and error string indicating more specific error information returned by the operating system. |
|
-5001 |
Generic error |
|
-5002 |
Failed reading media header. |
|
-5003 |
Failed installing kernel. |
|
-5004 |
Failed starting kernel. |
|
-5005 |
Failed opening CAB. |
|
-5006 |
Failed installing support. |
|
-5007 |
Failed setting text substitution. |
|
-5008 |
Failed initializing installation information. |
|
-5009 |
Failed getting installation driver. |
|
-5010 |
Failed initializing properties. |
|
-5011 |
Failed running installation driver. |
|
-5012 |
Failed uninstalling support. |
|
-5013 |
Failed to extract file from setup boot file. |
|
-5014 |
Failed to download file (occurs only when saving installation files during an Internet installation). |
|
-5017 |
Could not clone the installation. |
|
-6001 |
Failed starting the setup launcher. |
|
-6002 |
Failed finding the setup launcher. |
|
-6003 |
Failed loading the setup launcher. |
|
-6004 |
Failed verifying the signature of setup launcher. |
|
-6005 |
Failed installing the setup launcher to proper location. |
|
-6006 |
Failed extracting setup launcher. |
Typically, any time one of the error messages in the previous table is displayed, it is accompanied by one of the HRESULT values in the following table. These HRESULT values provide additional information about the cause of the error.
|
HRESULT |
Meaning |
|
0x80041F40 |
Cannot find corecomp.in.i |
|
0x80041F41 |
corecomp.ini is empty or corrupted. |
|
0x80041F42 |
Cannot load the .dll file inIsCoGetClassObject. |
|
0x80042328 |
Media is not signed. |
|
0x80042329 |
Certificate is invalid. |
|
0x8004232A |
Digital signature is invalid. |
|
0x8004232B |
Space is insufficient. |
|
0x80042A94 |
The specified opType’s main opsequence is not present in the log, such as when an old file is opened with the new engine, and the new (engine) code tries to get an opsequence for the newly introduced opType. |
|
0x80042A95 |
Failed to (re)construct a feature log’s full ID. |
|
0x80042A96 |
A log operation was attempted without opening the log file. |
|
0x80042A97 |
Internal opsequence structure initialization failed. |
|
0x80042A98 |
General failure in Opsequence::GetNext |
|
0x80042A99 |
General failure in Opsequence::Pop |
|
0x80042A9A |
General failure in Opsequence::insert_sequencetuple |
|
0x80042A9B |
General failure in Opsequence::delete_sequencetuple |
|
0x80042A9C |
Property initialization failure - could occur when setting/getting a property in the LogDB or Feature object. |
See Also
Setup.exe Return Values and Run-Time Errors (Basic MSI and InstallScript MSI Projects)
InstallShield 2015 Help LibraryJune 2015 |
Copyright Information | Contact Us |