Setup.exe Return Values and Run-Time Errors (Basic MSI and InstallScript MSI Projects)

InstallShield 2012 Spring

Project: This information applies to the following project types:

Basic MSI
InstallScript MSI

Note that project-specific differences are explained where applicable.

The table below lists the errors that might occur when Setup.exe from a Basic MSI or InstallScript MSI project is run. For Setup.exe errors that might occur for an InstallScript project, see Setup.exe Return Values and Run-Time Errors (InstallScript Projects).

You can capture these return values when you call the CreateProcess API to launch Setup.exe, or use a batch file to launch Setup.exe.

Note: If an error occurs on a non-English system, the error strings may not be displayed in English.

Setup.exe Run-time Errors and Return Values

Error or Status Number

Message

Troubleshooting Tips

-4

Invalid command line.

Project: This is applicable to InstallScript MSI projects.

Verify that a valid command line is passed to Setup.exe.

-3

The installation exited because the end user canceled the installation.

Project: This is applicable to InstallScript MSI projects.

-1

General error.

Project: This is applicable to InstallScript MSI projects.

0

Program terminated successfully.

Not applicable.

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.

Windows Installer is compatible with NT 4.0 and later, and Windows 9x and later. Check your version of Windows and upgrade if necessary.

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.

Run the setup and select another language.

1603

General Windows Installer engine error. Increase DiskSpace requirement in Setup.ini and try again.

Project: This is applicable to Basic MSI projects.

Reinstall Windows Installer.

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.

Project: This is applicable to InstallScript MSI projects.

1629

Invalid command line.

Double-check the command-line statement used to launch Setup.exe.

1641

The installation was successful and it required a restart.

Project: This is applicable to InstallScript MSI projects.

If the Windows Installer engine returns ERROR_SUCCESS (0), the Setup.exe file may return ERROR_SUCCESS_REBOOT_INITIATED (1641). This return value occurs if the installation itself is restarting the machine because the System function was called—typically as a result of the SdFinishReboot function calling System internally.

1670

Unable to load module [1], Error Code: [2]

[1] is the full path to the .dll file that the installation is attempting to load (ISSetup.dll in all cases).

[2] 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.

Project: This is applicable to InstallScript MSI projects.

This error indicates that a problem occurred when the InstallScript engine was being loaded.

1701

Unable to extract InstallScript engine support files to temp location.

Project: This is applicable to InstallScript MSI projects.

This error occurs if one or more files could not be extracted from the ISSetup.dll file to a temporary directory.

To troubleshoot this error, create a Windows Installer log file to obtain more information. The log file has the corresponding Windows error number and other diagnostic information that may help troubleshoot this issue.

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.

3010

The installation was successful and a restart is required to complete the installation.

Project: This is applicable to InstallScript MSI projects.

If the Windows Installer engine returns ERROR_SUCCESS (0), the Setup.exe file may return ERROR_SUCCESS_REBOOT_REQUIRED (3010). This indicates that installation required a restart but the installation is not initiating the restart. In this case, the installation completed with BATCH_INSTALL set to a non-zero value, but the System function was not called.

See Also