Did this article resolve your question/issue?



How to identify why a Silent installation fails?

« Go Back


TitleHow to identify why a Silent installation fails?
URL Name19657
Article Number000120498
EnvironmentProduct: Progress
Version: 9.1D, 9.1E
Product: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Other: Silent Install
Question/Problem Description
What do the InstallShield Silent Result Codes Mean?
What do the InstallShield Result Codes Mean?
What does the different ResultCode from the Silent Installation log mean?
How to identify why a silent installation fails?
How can one know if a silent installation is successful?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
The InstallShield Silent (ISS) Utility allows installing Progress OpenEdge in silent or batch mode by recording installation input information to a response file that can be run later with the -s command line parameter. Sometimes this fails and gives an error.

When this occurs, start the silent installation use the optional -f2C:\<path-to-file>\setup.log parameter in order to create a log file. The path-to-file indicates the location of the setup file. This InstallShield log file will contain an error message with a return code: "InstallShield failed (resultcode = xx)".

Common ResultCode values:
 0 Success.
-1 General error.**
-2 Invalid mode.
-3 Required data not found in the Setup.iss file.
-4 Not enough memory available.
-5 File does not exist.
-6 Cannot write to the response file.
-7 Unable to write to the log file.
-8 Invalid path to the InstallShield Silent response file.
-9 Not a valid list type (string or number).
-10 Data type is invalid.
-11 Unknown error occurred during setup.
-12 Dialog boxes are out of order.
-51 Cannot create the specified folder.
-52 Cannot access the specified file or folder.
-53 Invalid option selected.

  1. The Custom install type: As of OpenEdge version 10.1B, a silent installation supports either a Complete or Custom installation, previously only Complete and Typical install types are supported. 
  2. If the installation is successful but a reboot is required, the log file will record a return value of -1, (General error) **
  3. For additional troubleshooting provide the setup.iss and setup.log to Technical Support.
References to Other Documentation: 

Progress Installation and Configuration Guide for Windows - Section 2.10, " InstallShield Silent (Batch Mode) Utility"
OpenEdge Getting Started: Installation and Configuration - Performing an OpenEdge Installation in Windows -> OpenEdge Silent installation overview

Progress Article(s):

000011027, How to perform a silent install of Progress 9 or Openedge 10.0B or earlier on Windows   
000011151, Performing a silent install of OpenEdge 10.1A and above on Windows   

Last Modified Date4/24/2017 3:36 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.