This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- 1158 Error Solution
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 16, 2010
12:58 PM
How do I prevent error 1158?
Sometimes, when running a Basic MSI installation with setup.exe bootstrapper created in InstallShield 2009, an error dialog will appear containing the text "1158", an OK button, and nothing else. InstallShield error 1158 means there was a problem with loading strings from the associated ini file, but the troubleshooting steps have not worked for me. Also, I doubt that there is actually a problem with the strings; the information on that page suggests that a problem with strings would not be intermittent.
Here are the results of my investigation so far:
Has anyone else encountered this problem or know of a fix?
Here are the results of my investigation so far:
- The problem occurs before any other dialogs are displayed (including the prerequisites dialog), which leads me to believe this is a problem with the bootstrapper (setup.exe), not Windows Installer.
- The problem is intermittent, occurring frequently on some machines and almost never on others.
- The problem is not related to a particular build of the installation. The same setup.exe might fail one time and succeed if run again on the same machine.
- The problem appears to be related to Windows Explorer. I've never been able to reproduce this by launching the setup.exe through other means (e.g. cmd.exe). This hampers debugging efforts, since passing command line arguments to generate debug logs causes the installation to succeed.
- I've only seen this problem on Windows XP. This may not mean anything since newer versions of Windows are not used often within my company.
Has anyone else encountered this problem or know of a fix?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 07, 2010
12:45 PM
Answer is posted at stackoverflow.