InstallShield 2019
Project • This information applies to the following project types:
| • | Advanced UI |
| • | Suite/Advanced UI |
Edition • The Advanced UI project type is available in the Professional edition of InstallShield. The Suite/Advanced UI project type is available in the Premier edition of InstallShield. For information about the differences between these two project types, see Advanced UI Projects vs. Suite/Advanced UI Projects.
The table below lists the errors that might occur when an end user runs an Advanced UI or Suite/Advanced UI Setup.exe installation. The Type of Code column in this table indicates the following information:
| • | Exit code only—The installation status is returned by the Advanced UI or Suite/Advanced UI Setup.exe file. |
| • | Error code/exit code—The installation status is processed for evaluated error conditions, and the status is returned by the Advanced UI or Suite/Advanced UI Setup.exe file. |
| • | Logged only—The installation status is logged when debug logging is enabled. (Debug logging is enabled when the /debuglog command-line parameter is passed to the Advanced UI or Suite/Advanced UI Setup.exe file to launch the Advanced UI or Suite/Advanced UI installation. For more information on command-line parameters, see Advanced UI and Suite/Advanced UI Setup.exe Command-Line Parameters.) |
Note • Some of the error messages may be displayed before any string entries are available to the running Advanced UI or Suite/Advanced UI Setup.exe file. Therefore, in such cases (for example, Setup.xml is missing, another instance of the Advanced UI or Suite/Advanced UI installation is already running, or condition validation failed), those particular resulting error messages are displayed in English. Other errors that occur before language selection are typically displayed in the default setup language.
|
Status Code |
Type of Code |
Message |
Troubleshooting Tips |
|||
|
0x80040701 |
Exit code only |
Failed to read or initialize setup state information; missing SuiteId attribute on setup.xml setup element. Contact your vendor for assistance. |
The value of the SuiteID attribute in the Setup.xml file indicates the Suite GUID, as defined in the General Information view of the project. If this GUID is somehow removed from the Setup.xml file, this error may occur at run time. To resolve this error, try rebuilding the Advanced UI or Suite/Advanced UI installation. |
|||
|
0x80040702 |
Exit code only |
No UI DLL was loaded and initialized, possibly due to a missing UI resource. Contact your vendor for assistance. |
This exit code occurs if the UIResource definition in the project or the Setup.xml file is missing or invalid (for example, for a corrupted project). |
|||
|
0x80040705 |
Exit/error code |
MD5 check failed for the current file to be staged. The file may be corrupted. |
An Advanced UI or Suite/Advanced UI installation uses MD5 checks the integrity of the packages in the Advanced UI or Suite/Advanced UI installation. If the MD5 check fails, this error occurs. To resolve this error, try rebuilding the Advanced UI or Suite/Advanced UI installation. |
|||
|
0x80040706 |
Exit code only |
No setup.xml file was found in the running suite setup. Contact your vendor for assistance. |
This status code occurs if the Setup.xml resource could not be found. |
|||
|
0x80040707 |
Logged only |
Failed to extract a file that is necessary to run this setup. Contact your vendor for assistance. |
The log includes this status code if a resource that is listed in the Resources section of the Setup.xml file could not be extracted from the running Advanced UI or Suite/Advanced UI Setup.exe file. Check for build errors and the Support Files view for missing resources, and add them as needed. |
|||
|
0x80040708 |
Logged only |
Failed to copy or download a file that is necessary to run this setup. Contact your vendor for assistance. |
The log includes this status code if a resource that is listed in the Resources section of the Setup.xml file could not be copied or downloaded. Check for build errors and the Support Files view for missing resources, and add them as needed. |
|||
|
0x80040709 |
Error code only |
Failed to extract a file while staging. Either the file is not present in the stream or the file could not be written to the target machine. |
This error occurs if the Advanced UI or Suite/Advanced UI installation fails to stage a file that is streamed into the Advanced UI or Suite/Advanced UI Setup.exe file. Either the installation is corrupted or the file was missing at build time. |
|||
|
0x8004070A |
Exit/error code |
The setup password is incorrect or was not entered. The setup cannot proceed. |
The Setup.exe tab for a release in the Releases view of an Advanced UI or Suite/Advanced UI project lets you specify whether you want to password protect the setup launcher; if you do, you can also specify the password that end users need to enter in order to run the installation. This error occurs if there is no prompt for a password from the user interface during the preinstall phases of the installation. This can occur if a custom UI DLL is used and the end user tries to avoid the password prompt. This can also occur if an end user launches a password-protected Advanced UI or Suite/Advanced UI installation silently from the command line but does not include a password on the command line. |
|||
|
0x8004070B |
Exit/error code |
The setup command line is invalid. The setup cannot proceed. |
This error occurs if you pass an invalid command-line parameter to the Advanced UI or Suite/Advanced UI Setup.exe file while launching it from the command line. For a list of valid command-line parameters, see Advanced UI and Suite/Advanced UI Setup.exe Command-Line Parameters. |
|||
|
0x8004070C |
Exit/error code |
The setup could not start in a temporary folder. Contact your vendor for assistance. |
This error occurs if the Temp folder on the target system is full. To resolve this error, consider freeing space in the Temp folder. |
|||
|
0x8004070D |
Exit/error code |
The destination folder that was entered for a staging-only operation could not be created. |
When you are running an Advanced UI or Suite/Advanced UI installation with the /stage_only command-line parameter, the Advanced UI or Suite/Advanced UI installation attempts to copy its packages to a directory that is specified by the user. The directory must exist; if it does not, the installation encounters this error. To resolve this error, ensure that the path that you specify on the BrowseStageFolder wizard page exists. If it does not, create it and then rerun the installation. |
|||
|
0x8004070E |
Exit/error code |
An unknown failure occurred attempting to cache a file from either a remote server or a local path. Contact your vendor for assistance. |
If the file is located on a Web server, ensure that it is available on the machine where the installation is encountering this error. If the file is located on source media, ensure that the source media is available and valid. Check a debug log for any additional information that might be available. |
|||
|
0x8004070f |
Exit/error code |
An invalid condition was encountered while parsing setup.xml. Create a debug log to see if further information is available. The condition needs to be corrected in the IDE for the suite to launch successfully. |
This error occurs if an invalid condition was configured. To troubleshoot this error, check the debug log file for additional information. To learn more, see Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation. To resolve this error, edit the invalid condition in your Advanced UI or Suite/Advanced UI project. |
|||
|
0x80040710 |
Error Code |
The setup was aborted because the suite requirements defined in abort conditions were not met. |
This error occurs if the exit conditions that were defined in the General Information view were not met at run time on the target system. If this is unexpected, you may need to modify your exit conditions. To learn more, see Defining Exit Conditions for an Advanced UI or Suite/Advanced UI Installation |
|||
|
0x80040711 |
Exit/error code |
Another instance of the suite installation is already running. Please wait for the other instance to finish and then try again. |
Only one instance of an Advanced UI or Suite/Advanced UI installation can run on a target system at a time. |
|||
|
0x80040712 |
Exit/error code |
Failed to load ISSetup.dll to launch an InstallScript parcel. |
This error may occur if one or more of the files for an InstallScript package that is included in the project are not available to InstallShield at build time. To resolve this error, ensure that all of the files in your InstallScript package are available at build time. |
|||
|
0x80040713 |
Exit/error code |
Failed to call ISSetup.dll to launch an InstallScript parcel. Ensure the InstallScript setup contained in the parcel was built with a version of InstallShield that supports InstallScript parcels. |
This error may occur if you include in your project an InstallScript package that was built in InstallShield 2012 Spring or later. For additional requirements, see Adding an InstallScript Package to an Advanced UI or Suite/Advanced UI Project. |
|||
|
0x80040714 |
Exit/error code |
Failed to launch EXE. This error can occur when attempting to launch EXE actions, elevated EXE parcels, or Windows Features support on Windows Vista, 2008, 7, or 2008 R2 and the EXE fails to launch. Check a debug log as this may contain more detailed error information. |
To troubleshoot this error, check the debug log file for additional information. To learn more, see Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation. |
|||
|
0x80040715 |
Exit/error code |
Failed to load DLL. This error can occur when attempting to load a DLL for DLL actions or Windows Features support on Windows 8 or newer versions of Windows. Check a debug log as this may contain more detailed error information. |
This error may occur if the file that a DLL action in your project needs to call is missing or could not be loaded. This may also occur if the installation is attempting to enable Windows roles or features on a target system. To troubleshoot this error, check the debug log file for additional information. To learn more, see Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation. |
|||
|
0x80040716 |
Exit/error code |
Failed to locate or load support files needed to run a PowerShell action. Check a debug log as this may contain more detailed error information. |
This error may occur if the file that a PowerShell action in your project needs to call is missing or could not be loaded. To troubleshoot this error, check the debug log file for additional information. To learn more, see Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation. |
|||
|
0x80040718 |
Exit/error code |
Failed to call InstallScript function in InstallScript action. Check a debug log as this may contain more detailed error information. |
This error occurs because the installation could not call an InstallScript function in an InstallScript action. To troubleshoot this error, check the debug log file for additional information. To learn more, see Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation. |
|||
|
0x8004071A |
Error code |
The path specified for a suite debug log does not exist or is invalid. Specify a valid file path when passing /debuglog with a file path. The suite error returned in this case is 1622. |
Ensure that you specify a valid path for the debug log file. |
|||
|
0x8004071B |
Exit/error code |
A resource required to install a web deploy parcel was not found. Rebuild the setup and try again. |
This error may occur if the file that a Web Deploy package in your project requires is missing. To troubleshoot this error, check the debug log file for additional information. To learn more, see Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation. |
|||
|
0x8004071C |
Exit/error code |
A resource required to call a CLR action is missing or failed to load. Check a debug log as this may contain more detailed error information. |
This error may occur if the file that a managed-code action in your project needs to call is missing or could not be loaded. To troubleshoot this error, check the debug log file for additional information. To learn more, see Troubleshooting Issues with an Advanced UI or Suite/Advanced UI Installation. |
|||
|
0x8007007f |
Error code only |
The specified procedure could not be found. |
This error is system error 127. This error may occur if the Advanced UI or Suite/Advanced UI installation is run on a system that does not meet the minimum requirements for Windows Installer:
|
|||
|
0x8007007f (cont.) |
|
|
This error may also occur if the Advanced UI or Suite/Advanced UI installation has trouble installing an InstallScript package because the package was built in InstallShield 2012 or earlier. For more information, see Adding an InstallScript Package to an Advanced UI or Suite/Advanced UI Project. In addition, this error may occur if there is a problem with an Advanced UI or Suite/Advanced UI extension condition. If your project includes an extension condition, check to ensure that the DLL for the extension condition has the proper exported entry points. |
See Also
Creating Advanced UI and Suite/Advanced UI Installations
InstallShield 2019 Help LibraryApril 2019 |
Copyright Information | Flexera |