InstallAnywhere 2017
The command-line build tool returns an exit code based upon the results of the build as follows.
|
Code |
Status |
||||||||||||
|
Resource Related |
|||||||||||||
|
cancelled1 |
Missing resources, build abort canceled by preferences |
||||||||||||
|
Project File Related |
|||||||||||||
|
101 |
Project load error |
||||||||||||
|
102 |
Project copy load error |
||||||||||||
|
103 |
Project file not found |
||||||||||||
|
104 |
Project file is read-only |
||||||||||||
|
199 |
Project file unknown error |
||||||||||||
|
Command-Line Options Related |
|||||||||||||
|
200 |
Illegal build flag |
||||||||||||
|
201 |
Insufficient build flag |
||||||||||||
|
VM Pack Related |
|||||||||||||
|
300 |
VM Pack replaced |
||||||||||||
|
301 |
VM Pack not found |
||||||||||||
|
302 |
VM Pack illegal format |
||||||||||||
|
399 |
VM Pack unknown error |
||||||||||||
|
File Write Errors |
|||||||||||||
|
400 |
File write not found |
||||||||||||
|
401 |
File write busy |
||||||||||||
|
402 |
File write protected |
||||||||||||
|
403 |
File write error |
||||||||||||
|
499 |
File write unknown error |
||||||||||||
|
File Read Errors |
|||||||||||||
|
500 |
File read not found |
||||||||||||
|
501 |
File read busy |
||||||||||||
|
502 |
File read protected |
||||||||||||
|
503 |
File read error |
||||||||||||
|
599 |
File read unknown error |
||||||||||||
|
Errors with Digitally Signing Windows-Based Installers |
|||||||||||||
|
801 |
To resolve this error, check the values that you entered in the Digital Signing area in the Platforms view on the Project page, and make corrections as needed. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
802 |
To resolve this error, check the values that you entered in the Digital Signing area in the Platforms view on the Project page, and make corrections as needed. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
803 |
To resolve this error, check the values that you entered in the Digital Signing area in the Platforms view on the Project page, and make corrections as needed. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
804 |
To resolve this error, check the values that you entered in the Digital Signing area in the Platforms view on the Project page, and make corrections as needed. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
805 |
To resolve this error, check the values that you entered in the Digital Signing area in the Platforms view on the Project page, and make corrections as needed. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
806 |
This build error occurs if InstallAnywhere encounters an issue reading the certificate file that is configured for digitally signing Windows-based installers. To resolve this error, check the values that you entered in the Digital Signing area in the Platforms view on the Project page, and make corrections as needed. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
807 |
To resolve this error, check the values that you entered in the Digital Signing area in the Platforms view on the Project page, and make corrections as needed. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
808 |
This build error may occur if the digital certificate password that was specified in InstallAnywhere does not match the password that was set up for the certificate file. To resolve this error, check the values that you entered in the Password setting (Project page > Platforms view > Windows area > Digital Signing area), and make corrections as needed. If the values in those settings are correct, try regenerating the certificate file (.pfx). To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
809 |
To resolve this build error, ensure that the password that you entered in the Password setting (Project page > Platforms view > Windows area > Digital Signing area) matches the password that was set up for the certificate file. Also ensure that the build machine can access the timestamp server that is specified in the Digital Signing area. If the settings are configured correctly and the build machine can access the timestamp server, try regenerating the certificate file (.pfx). To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
810 |
This build error occurs if the timestamp server is not available to the build machine, and InstallAnywhere cannot timestamp the digitally signed Windows-based installers. To resolve this error, ensure that the build machine can access the timestamp server that is specified in the Digital Signing area. If it cannot, try a different timestamp server. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
811 |
This build error may occur if the build machine cannot access the certificate file that was specified in the Certificate File setting (Project page > Platforms view > Windows area > Digital Signing area). To resolve this error, ensure that the specified path and file name are correct, and that all users have read permission for the file. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
812 |
This build error occurs if InstallAnywhere is able to digitally sign the Windows-based installers but cannot timestamp the signed files. Skipping timestamping may affect how long your digital signature is considered to be valid. To resolve this error, ensure that a valid and available timestamp server is specified in the Timestamp Server setting (Project page > Platforms view > Windows area > Digital Signing area). If necessary, try a different timestamp server. To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
813 |
This build error occurs if a SHA-1 digital certificate was configured to be used to digitally sign the Windows-based installers at build time. Windows will not trust files that were signed with SHA-1 certificates if they were signed after January 1, 2016. SHA-2 is favored over SHA-1, which is being deprecated because of the potential for security vulnerabilities. Thus, it is recommended that you replace any SHA-1 certificates in your InstallShield projects with SHA-2 certificates. To replace the SHA-1 certificate with a SHA-2 certificate, specify a SHA-2 certificate in the Certificate File setting (Project page > Platforms view > Windows area > Digital Signing area). To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
814 |
This build error occurs if the following conditions are true:
Windows will not trust files that were signed with SHA-1 certificates if they were signed after January 1, 2016. SHA-2 is favored over SHA-1, which is being deprecated because of the potential for security vulnerabilities. Thus, it is recommended that you replace any SHA-1 certificates in your InstallShield projects with SHA-2 certificates. To resolve this error:
To learn more, see Digitally Signing Windows-Based Installers. |
||||||||||||
|
Other |
|||||||||||||
|
-1 |
Other error/unknown error |
||||||||||||
|
0 |
No errors. Build completed successfully without errors or warnings |
||||||||||||
|
666 |
Insufficient rights in directory |
||||||||||||
|
799 |
Unknown internal error |
||||||||||||
See Also
InstallAnywhere Ant Task Reference
InstallAnywhere 2017 Help LibraryNovember 2016 |
Copyright Information | Flexera Software |