Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error 1155

Error 1155


When running an installation, the following error occurs:


When running an installation, the following error occurs:

  • Error 1155: File <FILENAME> not found.
  • Error 1155: Error extracting to Temp directory.
  • A dialog may also appear which does not name the missing file.
<FILENAME> contains the specific file that cannot be found.


There are a few known causes for this error. Please see the potential causes and solutions below.


Installation is Built Without Including the Windows Installer Engine. This error occurs on machines other than Windows 2000 or XP, where the Windows Installer is not pre-installed. The error only occurs if the installation is run via Setup.exe. Because Windows Installer packages require the Windows Installer engine on the machine prior to running the package, the installation attempts to install the Windows Installer engine on the machine at the beginning. In your build option, if you deselect the Windows Installer engines from being included in the installation, it errors out with error 1155. In the properties of the Release, make sure the Include MSI Engine(s) attribute is set to Both 9x and NT Engines. This attribute should not be set to None, as that causes the error message.
Occurs on reboot. This error occurs on a machine that does not have MDAC installed on it. Typically, after an installation installs MDAC on the machine, it triggers a reboot and then attempts to launch the installation again after reboot, when it fails with error 1155.
This normally happens if the Temp directory is not clean. Clean your Temp directory and run setup.exe again on reboot to eliminate the error message.
Running an installation from a CD. To eliminate Error 1155 that occurs with an installation being run from a CDROM, copy all the files from the CDROM to the local drive of the machine and run it from there. After copying all the files from the CD, make sure that they are not read-only. To ensure that a file is not read-only, right-click it in Windows Explorer and select Properties. Clear the Read-only check box.
The File Specified in the Error is Not Located on the Source Media. To resolve this behavior, Verify that the MSI file is in the same folder as the setup.exe file on the source media. The MSI file may not appear in the same folder as the setup.exe file if you opted to compress the media in the Release settings. In that situation, it would be compressed into the setup.exe file itself. Make sure the file specified in the error is actually located in the expected location.
Terminal Services set to 'Delete Temp Folders Upon Exit'
According to the Microsoft KB article Q294751, normally Terminal Server session temporary directories are removed by WINLOGON when a user logs off or the session is reset. However, the package being installed resides in a temporary directory during a reboot.
Microsoft offers functionality in the Terminal Services Group Policy Objects described as: Do not delete temp folders upon exit. By enabling the persistance of the temporary directories, the installation process can continue normally.

The functionality of Terminal Services is outside of the InstallShield application. Performance, behaviour and documentation for third-party applications should be pursued with the appropriate vendor.

Additional Information

This error message is stored in an initialization file located in the same folder as the setup.exe file. This file is named after the language ID for the desired language. For example, the English version of this error message is stored in the file called 0x0409.ini. This file can be opened in any text editor such as Notepad or Microsoft Word, and the text of the message can be modified.
Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Oct 31, 2007 06:20 PM
Updated by: