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
- :
- InstallScript Setup Launcher Unicode Has Stopped Working (Windows message)
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
Sep 06, 2013
06:06 PM
InstallScript Setup Launcher Unicode Has Stopped Working (Windows message)
InstallScript based setup, upgraded from IS 2011 setup but no other changes to the setup.
A small number of customers in the field (5% or less) are now seeing this error when trying to install. It happens at the "Preparing Setup" stage of the wizard, after selecting which language to use. Running the setup again does not allow it to succeed. No InstallShield error is displayed just the Windows error.
The setup has InstallScript to read a file for a license key, but this will display a message box if there are problems reading that file (I've verified that my message box appears if this fails). The script code also sets a few registry keys. There are no custom DLLs or anything else "tricky."
I moved to a new PC and in the process switched from InstallShield 2011 Premiere to IS 2013 Premiere. This unfortunately means I no longer have IS 2011 installed.
Any ideas on how to diagnose and fix this are welcome.
A small number of customers in the field (5% or less) are now seeing this error when trying to install. It happens at the "Preparing Setup" stage of the wizard, after selecting which language to use. Running the setup again does not allow it to succeed. No InstallShield error is displayed just the Windows error.
The setup has InstallScript to read a file for a license key, but this will display a message box if there are problems reading that file (I've verified that my message box appears if this fails). The script code also sets a few registry keys. There are no custom DLLs or anything else "tricky."
I moved to a new PC and in the process switched from InstallShield 2011 Premiere to IS 2013 Premiere. This unfortunately means I no longer have IS 2011 installed.
Any ideas on how to diagnose and fix this are welcome.
(12) Replies