3 replies to this topic

[overlord]

I have inherited an old ism project from Installshield 2012. If I build the MSI release in the product configuration it builds it and signs it no problem. If however I attempt to create a release or using the existing release for the setup.exe where it signs both the exe and the msi it crashes installshield immediately after signing the msi file. If I tell it to only sign the exe and not the installer package it will not crash the UI but then the msi is not signed.

 

I have tried creating new product configurations as well as removing things like chained msi's, redistributables etc. I have also contacted flexera but their stance is "you need to upgrade as 2012 is no longer a supported product" The issue is if I upgrade even this one project I have to upgrade a ton of them because the old build server can only be pointed at one version of installshield. That introduces a ton of variables I am not really comfortable dealing with. If you have any idea as to what could be causing this please let me know.

Exception ACCESS_VIOLATION (0xc0000005)
 at address 0x75182ed4 trying to read address 0x00000001.
 
File           : C:\Program Files (x86)\InstallShield\2012\System\isdev.exe
Version        : 18.0.0.329
Exception      : c0000005
Address        : 75182ed4
Access Type    : read
Access Address : 00000001
 
Registers      : EAX=00000001 CS=0023 EIP=75182ed4 EFLGS=00010202
               : EBX=00000000 SS=002b ESP=0018d1a0 EBP=0018d9bc
               : ECX=00000000 DS=002b ESI=75174cb0 FS=0053
               : EDX=000a0000 ES=002b EDI=0018d9fc GS=002b
 
Stack Trace    : 75172acd 64dd7f61 64e91821 64e8e9fe
               : 00000000 64fb89e0 00000018 00000000
               : 00000000 00000000 00000000 00000000
               : 00000000 00000000 00000000 00000000
               : 00000000 00000000 00000000 00000000
               : 00000000 00000000 00000000 00000000
               : 00000000 00000000 00000000 00000000
               : 00000000 00000000 00000000 00000000
 

[deramor]

Recently, Root Certificate Authorities switch to using SHA256 hash algorithms when creating certificates.  Was your certificate recently renewed?

 

Without changes, IS2015 does not support signing and time stamping using a SHA256 certificate.

 

You may want to disable signing and perform the signing manually in your build process.  You can also change a config file in the Installshield folder to use different settings to perform the signing.  It is something to try at least.

[overlord]

so it was renewed last year sometime I believe for 3 years. With that said, it only crashes when it signs the msi. If I sign the setup.exe without signing the msi it signs just fine. It only seems to crash when I attempt to sign the msi file. It reports that it signs it successfully then crashes immediately after with that access error. I have been stepping through windows updates that touch crypt files related to the -6003 error code to see if any of them are causing this. I uninstalled one of the patches and it actually triggered the same crash but way earlier in the call stack. Like as soon as it processes setup.inx or setup.rul

[Stefan Krueger]

Does signing manually using a command line tool work?

I'm not sure it this is possible in IS 2012, but in recent version you can specify build events on the Events tab of the Release settings. There you could call the signing exe as a precompression event.