Installer Exit Codes
InstallAnywhere 2020 SP2
By default, an installation process returns zero (0) to the environment if it was successful and a nonzero value if it was not. The following table describes the possible exit codes that may be returned during an installation.
|
Code |
Description |
|
0 |
Success: The installation completed successfully without any warnings or errors. |
|
1 |
The installation completed successfully, but one or more of the actions from the installation sequence caused a warning or a non-fatal error. |
|
-1 |
One or more of the actions from the installation sequence caused a fatal error. |
|
1000 |
The installation was canceled by the end user. |
|
1001 |
The installation includes an invalid command-line option. |
|
2000 |
Unhandled error. |
|
2001 |
The installation failed the authorization check, may indicate an expired version. |
|
2002 |
The installation failed a rules check. A rule placed on the installer itself failed. |
|
2003 |
An unresolved dependency in silent mode caused the installer to exit. |
|
2004 |
The installation failed because not enough disk space was detected during the execution of the Install action. |
|
2005 |
The installation failed while trying to install on a 64-bit Windows system, but installation did not include support for 64-bit Windows systems. |
|
2006 |
The installation failed because it was launched in a UI mode that is not supported by this installer. |
|
2009 |
Indicates that the user attempted to launch multiple instances of an installer at the same time even though the installer was configured to prevent multiple launches; the Prevent multiple launches of an installer at a given time check box was selected in the General Settings view on the Project page of this installer’s InstallAnywhere project. |
|
3000 |
Unhandled error specific to a launcher. |
|
3001 |
The installation failed due to an error specific to the lax.main.class property. |
|
3002 |
The installation failed due to an error specific to the lax.main.method property. |
|
3003 |
The installation was unable to access the method specified in the lax.main.method property. |
|
3004 |
The installation failed due to an exception error caused by the lax.main.method property. |
|
3005 |
The installation failed because no value was assigned to the lax.application.name property. |
|
3006 |
The installation was unable to access the value assigned to the lax.nl.java.launcher.main.class property. |
|
3007 |
The installation failed due to an error specific to the lax.nl.java.launcher.main.class property. |
|
3008 |
The installation failed due to an error specific to the lax.nl.java.launcher.main.method property. |
|
3009 |
The installation was unable to access the method specified in the lax.nl.launcher.java.main.method property. |
|
4000 |
A Java executable file could not be found at the directory that was specified by the java.home system property. |
|
4001 |
An incorrect path to the installer jar caused the relauncher to launch incorrectly. |
|
5000 |
Modification of existing instance failed because the instance has not been uninstalled properly or because the product registry has been corrupted. |
|
7000 |
The installation was rolled back due to a fatal exception. |
|
8000 |
The upgrade was canceled because a newer version of the product is already installed on the target system. |
|
8001 |
The end user canceled the upgrade. |
|
8002 |
The upgrade exited because the earlier version of the product could not be successfully uninstalled. |
Note:For information on exit codes from the command-line builder, see Build Exit Codes.
See Also
Installer and Uninstaller Command-Line Arguments