DebbieMurray asked a question.
"InstallScript setup launcher unicode has stopped working"
I created an installscript installer using InstallShield 2013 Pro which is distributed to our users.
One of our users is getting the error message: "Install script setup launcher unicode has stopped working" at the beginning of the install (after the maintain/update screen).
The error from the event viewer is as follows:
Log Name: Application
Source: Application Error
Date: 12/31/2013 9:43:42 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: finance-win7.cbts.local
Description:
Faulting application name: setup.exe_Church Windows Payroll, version: 14.0.11.0, time stamp: 0x51a6cc99
Faulting module name: ISSetup.dll, version: 20.0.0.376, time stamp: 0x51a6cc32
Exception code: 0xc0000005
Fault offset: 0x0001ab47
Faulting process id: 0x2c8
Faulting application start time: 0x01cf0636ad8f408d
Faulting application path: C:\Users\EHousel\Desktop\Install\setup.exe
Faulting module path: C:\Users\EHousel\Desktop\Install\ISSetup.dll
Report Id: f106c19d-7229-11e3-9ca4-6805ca183f73
Event Xml:
1000
2
100
0x80000000000000
11317
Application
finance-win7.cbts.local
setup.exe_Church Windows Payroll
14.0.11.0
51a6cc99
ISSetup.dll
20.0.0.376
51a6cc32
c0000005
0001ab47
2c8
01cf0636ad8f408d
C:\Users\EHousel\Desktop\Install\setup.exe
C:\Users\EHousel\Desktop\Install\ISSetup.dll
f106c19d-7229-11e3-9ca4-6805ca183f73
We have made sure that the following folders exist on their machine:
1. C: > Users > ("Yourname" Windows account ) > My Documents
2. C: > Users > ("Yourname" Windows account ) > AppData > Local
3. C: > Users > ("Yourname" Windows account ) > AppData > Roaming > Microsoft > Windows > Start Menu > Programs > Startup
4. C: > Users > Default > Documents
5. C: > Users > Default > AppData > Roaming > Microsoft > Windows > Start Menu > Programs > Startup
I'm not sure how to proceed from here and the customer is currently unable to install the update. Any suggestions?
Thank you,
Debbie Murray
Lets try to create a new folder c:\temp and set to it all rights. Put your setup intp this folder and start it new.
Thank you for your help. We had our user try this (created a temp folder with full permissions, copied installer to that folder, also ran as admin), but unfortunately they still get the same error. Any other suggestions?
Thank you!! That did indeed work, for two of our customers. I very much appreciate your help.
Debbie
Thank you again!
Debbie
I will try that, thank you. "
Was this ever solved? I had no problems with 2013, but I've upgraded to 2014, and now I see the error "Setup Launcher Unicode Has Stopped Working" when running the installer on Windows Server 2008.