QL412674 asked a question.
Installer generated from installshield2016 crashes right after launching in some machines not all
I have an installer that worked in some machines but failed in some. The installer won't launch and the Event Viewer shows the error log as below:
Faulting application name: _is6D5F.exe, version: 2.4.0.1, time stamp: 0x5906bdf7Faulting module name: Setup_UI.dll, version: 23.0.0.511, time stamp: 0x5906be93
Exception code: 0xc0000005
Fault offset: 0x0004176c
Faulting process id: 0x2b4c
Faulting application start time: 0x01d715c298f191b1
Faulting application path: C:\Users\KBOXA1~1\AppData\Local\Temp\{5ACCA17A-3E11-454D-8D8C-1A3948A630B3}\_is6D5F.exe
Faulting module path: C:\Users\KBOXA1~1\AppData\Local\Temp\{555562F1-FDBB-4443-8A75-E56B3F580DC6}\Setup_UI.dll
Report Id: c9582a60-ecee-4916-b7be-0116ab9e6dc0
Faulting package full name:
Faulting package-relative application ID:
Can you try and capture a log of the installation - this might provide more information as to what is failing.
You can log the Windows Installer Engine:
https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/enable-windows-installer-loggin
If you are using a setup bootstrapper (For Basic MSI, Installscript MSI and Suite projects) - you can also log that using:
Setup.exe /debuglog"C:\PathToLog\setupexe.log"
I turned on msi log and couldn't find the msi.log in %temp% folder
I ran setup.exe from the command line with debug and got the log as attached, the error part is below: (the entire file is attached)
-19-2021[12:33:55 PM]: Engine: we're not running after reboot
3-19-2021[12:33:55 PM]: Engine: property 'ProductName' value now 'Clariti Edge Device'
3-19-2021[12:33:55 PM]: Engine: property 'ProductVersion' value now '2.4.0-beta.1'
3-19-2021[12:33:55 PM]: Determining setup mode...
3-19-2021[12:33:55 PM]: Engine: no command line mode specified, evaluating setup.xml install mode block for mode
3-19-2021[12:33:55 PM]: Engine: failed to evaluate install mode 0 condition, error 80020005
3-19-2021[12:33:55 PM]: Engine: property 'ISInstallStatus' value now 'IDS_SUITE_INTERRUPTED'
3-19-2021[12:33:55 PM]: Engine: property 'ISParcelStatus' value now ''
3-19-2021[12:33:57 PM]: UI DLL: Shutting down
3-19-2021[12:33:57 PM]: Original exit status: 0x80020005, final exit status: 0x80020005
3-19-2021[12:33:57 PM]: State manager: removing staging files from: C:\Users\HPEEL3~1\AppData\Local\Temp\{6BF4243C-52D3-453E-AFA6-1CC9C70AC8AD}\
3-19-2021[12:33:57 PM]: State manager: removing state infoInstallShield
I found out if I use command line to build installer in CI pipeline like below:
"${env:ProgramFiles(x86)}\InstallShield\2016\System\IsCmdBld.exe" -p "$(Build.SourcesDirectory)\VOFEdgeSetup.issuite" -z ProductVersion=$(GitVersion.SemVer) -y $(GitVersion.SemVer)
the installer crashes at some machiens. but if I just use InstallShield UI to build, the installer runs fine everywhere.
But I need it to be in CI pipeline, that means I can only use command line.
Any help? please