I found the descriptions of the result codes . Here they ar if someone is interested! (besides me.)
<<<<<<-------------
The InstallShield Silent (ISS) Utility allows you to install Progress
in silent or batch mode by recording your 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.
This solution provides a brief explanation of these errors.
SOLUTION:
The InstallShield gives an error message with a return code, like:
"InstallShield failed (resultcode = xx)."
The "xx" in this example is numeric value :
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.
ADDITIONAL INFO:
- The custom install type is not supported for silent install.
Only Complete and typical are supported.
- If the installation is successful but a reboot is required, the log
file will record a return value of -1, (General error).
<<<<<<-------------
Here are the possible solutions for result codes = 12 :
<<<<<<-------------
The InstallShield Silent (ISS) Utility allows you to install Progress
in silent or batch mode by recording your installation input
information to a response file that can be run later with the -s
command line parameter. This Knowledge Based solution discusses some
workarounds for the RESULTCODE=-12 error that can occur.
SOLUTION 1:
If you do not have enough disk space you will get a resultcode of -12.
SOLUTION 2:
You might see a RESULTCODE of -12 if the silent installation procedure
does not use the same dialog sequence as the template installation, or
if an error causes the installation to be aborted.
In your SETUP.ISS, [DlgOrder] section of the utility you should have
something like the following:
[DlgOrder]
Dlg0=Welcome Dialog-0
Count=9
Dlg1=SerialControlNumber Dialog-0
Dlg2=TargetDirectory Dialog-0
Dlg3=UserInstallationType Dialog-0
Dlg4=SdSelectFolder-0
Dlg5=LanguageChoice Dialog-0
Dlg6=International Settings Dialog-0
Dlg7=SdShowInfoList-0
Dlg8=RebootDialog-0
If you should have a Count=10 and an additional Dlg2=MessageBox-0
line, it could be that:
- Your serial / control keys are wrong.
- An additional dialog has come up during the recording session.
Do the following:
1) Check to see if the serial and control codes are correct. They
are in the [SerialControlNumber Dialog-0] section and appear
as follows:
[SerialControlNumber Dialog-0]
nvCount=1
svSerialNumber-0=002784544
svControlNumber_1-0=Q6FSG
svControlNumber_2-0=EQR7M
svControlNumber_3-0=LGGYJ
2) If they are correct, then remove the extra line reading
"Dlg2=MessageBox-0".
3) Set the count=9 and re-number the lines in the [DlgOrder]
session.
Most likely some alert appeared during the recording
session and caused this additional entry to be placed in
the setup.iss file.
SOLUTION 3:
Make sure you do NOT use UNC file references to the setup.exe file.
Map a drive on the local installation machine to the directory in
which the Progress installation software is located.
Example:
Incorrect: \\anypc\91B\setup.exe -s -f1... -f2...
Corect : T:\setup.exe -s -f1... -f2...
SOLUTION 4:
Make sure to check the correctness of the WebServer installation
directory (if any) in the [WebServer Dialog-0] section. Look at the
'_szCGIScriptDir' and '_szDocRootDir' entries.
<<<<<<-------------
Hope is useful.
Bubu
].