This chapter contains relevant information about InstallShield errors that may occur. For complete information please refer to the InstallShield help files and/or reference manual.
setup.exe is the main setup executable; it performs setup initialization and launches the appropriate setup engine file on the target system.
Once you have built your setup, you can rename setup.exe to any valid file name, such as install.exe.
7.1.1 SyntaxSetup [switches]
The switches are optional. They are not case sensitive; upper or lower case letters can be used.
This is a Mimer SQL specific switch which specifies location and name of a reboot indicator log file.
"RebootNeeded=1" is inserted into the file if reboot is required to complete the installation.
"RebootNeeded=0" is inserted into the file if reboot is not required.
It is recommended that the reboot indicator log file and the log file are the same file.
/f or -f
Specifies an alternate compiled script.
Unless the compiled script (.ins file) also resides in the same directory as that of setup.exe, the full path to the compiled script must be specified.
_setup.dll must also reside in the same directory as your .ins file. For example, setup -ftest.ins will launch setup using Test.ins instead of Setup.ins.
/f1 or -f1
Specifies an alternate location and name of the response file (.iss file).
If this option is used when running InstallShield Silent, the response file is read from the folder/file specified by <path\ResponseFile>.
If this option is used along with the -r option, the response file is written to the
folder/file specified by <path\ResponseFile>.
If an alternate compiled script is specified using the -f switch, the -f1 switch entry must follow the -f switch entry.
/f2 or -f2
Specifies an alternate location and name of the log file created by InstallShield Silent.
By default, Setup.log log file is created and stored in the same directory as that of Setup.ins.
If an alternate compiled script is specified using the -f switch, the -f2 switch entry must follow the -f switch entry.
/r or -r
Causes setup.exe to automatically generate a silent setup file (.iss file), which is a record of the setup input, in the Windows folder.
/s or -s
Runs InstallShield Silent to execute a silent setup.
/z or -z
Prevents setup.exe from checking the available memory during initialization.
This switch is necessary when running a setup on a machine with more than 256 MB of disk space; if it is not used, setup.exe reports insufficient memory and exits.
Separate multiple command line switches with a space. But do not put a space inside a command line switch. For example, /r /fInstall.ins is valid, but not
When using long path and file name expressions with switches, enclose the expressions in double quotation marks. The enclosing double quotes tell the operating system that spaces within the quotation marks are not to be treated as command line delimiters.
setup.exe may produce error messages if it cannot start properly. In most cases you'll encounter these messages when a severe error occurs. Rarely will your end users see these messages.
Error messages are displayed in message boxes. Every error message has a number. These are InstallShield system error messages and there is no way to suppress them in your script.
7.1.5 setup.exe Error Codes
The following table explains setup.exe error codes:
-4 Invalid command line Verify that a valid command line is passed to Setup.exe. -3 The installation exited because the end user canceled the installation - -1 General error - 0 Program terminated successfully - 401 String variable is not large enough for string. InstallShield was attempting to copy a text string into a string variable. The text string was larger than the length declared for that string variable. Check the declared length of the string variable. Increase the length to the maximum allowed value. 1150 Setup has detected an incompatible version of Windows Click OK and relaunch the setup on Windows 95, Windows NT 4.0, or later. 1151 Error writing to the temporary location To write to the temporary location, the environment variable TEMP must be set. Verify that the Temp folder exists and has enough disk space to accommodate the setup. If there are files in the Temp folder, delete them and rerun Setup.exe. 1152 Error extracting <file name> to the temporary location Check to see that you are able to write to the Temp folder (see errors above). If the Temp folder is valid, there may be corrupted files in the setup. Check the files to ensure none are corrupted and rerun Setup.exe. 1153 Error reading setup initialization file The Setup.ini file must be located in the same folder as Setup.exe. If not, move Setup.ini to that location. 1154 Installer not found in <path> Windows Installer may not have been properly installed, or you may have an older version. Reinstall if necessary. 1155 File <file name> not found Make sure the .msi file exists. If so, make sure it is located in the same folder as Setup.exe. You may not see the .msi file if you chose to compress it into Setup.exe. 1156 Internal error in Windows Installer Windows Installer was unsuccessfully installed. Run the InstMsiW.exe file (for Windows NT and 2000) or InstMsiA.exe (for Windows 9x) to reinstall. 1157 Failed to launch Msiexec.exe. Make sure you distribute the correct version of Windows Installer for the target platform.Check the syntax on your Msiexec.exe command-line arguments. 1158 Error populating strings Verify that all strings in Setup.ini and any language-specific INI files in the Disk1 folder (such as 0x0409.ini) are valid. 1201 Setup needs <amount> KB free space in <folder> Please free up some space and try again. There is insufficient disk space in your target location. Please make sure there is at least 10 MB of free space in the drive where the setup is set to install. 1202 You do not have sufficient privileges to complete this installation for all users of the machine Log on as an administrator and then retry this installation. In Windows NT 4.0 and 2000, you must have administrative rights to complete this installation. 1203 Invalid command-line parameters Double-check the command-line statement used to launch Setup.exe. 1207 Windows Installer <version> not found This is an older version of Windows Installer. Click OK to continue. In Windows 2000 and later, Windows Installer is installed by default. If the end user's version of Windows Installer is an earlier version, this warning is displayed. It should not prevent the setup from running correctly.To suppress this warning, select the current release's icon in the Releases view, and change the Suppress Launcher Warning setting to Yes. 1208 ANSI code page for <language> is not installed on the system and therefore setup cannot run in the selected language Run the setup and select another language. 1603 General Windows Installer engine error Increase DiskSpace requirement in Setup.ini and try again.Reinstall Windows Installer by running InstMsiW.exe file (for Windows NT and 2000) or InstMsiA.exe (for Windows 9x) to reinstall. 1611 Unable to extract the file <filename> This error occurs when a file compressed inside Setup.exe cannot be extracted. Verify that there is sufficient disk space available in the Temp folder (or, if not, in the Windows or WinNT folder), and that Setup can write to those folders. 1614 An error occurred while downloading the file <filename> If the URL is incorrect, click Cancel and enter the correct URL.If the URL is correct, verify that an active Internet connection is available. 1621 Failed to verify signature of file <filename> The file was downloaded, but the signature could not be verified. The file might be corrupted, it might have been signed by a different company than originally signed it, or it might not be signed.Verify that the file Wintrust.dll exists on the target system. 1627 Unable to save file: <filename> Ensure that the specified file does not already exist, and that the target system has sufficient hard drive space. 1628 Failed to complete script based install. - 1629 Invalid command line Double-check the command-line statement used to launch Setup.exe. 1670 Unable to load module , Error Code:   is the full path to the .dll file that the installation is attempting to load (ISSetup.dll in all cases). is the Windows error returned from LoadLibrary().This error occurs if ISSetup.dll is not in the Disk1 folder. It also may occur if ISSetup.dll is compressed in Setup.exe if a compressed media is being built.To resolve this error, try rebuilding the release. 1700 An error occurred initializing the InstallScript engine This error indicates that a problem occurred when the engine was being loaded. 1701 Unable to extract InstallScript engine support files to temp location This error occurs if one or more files could not be extracted from the ISSetup.dll file to a temporary directory. 1919 Error configuring ODBC data source Verify that the file exists and that you can access it.Machines running Windows 95 do not have the ODBC core. You need to install MDAC before installing any package with an ODBC driver.
7.1.6 Setup Runtime Errors
When copying the installation files the following errors may occur. These error numbers will occur in the ResultCode in the response file.
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 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.
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40