Exception ACCESS_VIOLATION (0xc000006) at address 0xXXXXXXXXX to read address 0xc000000

[Amit_pu]

Hi Team,

I have recently upgraded my InstallShield Professional from 2012 to 2019 on Windows Server 2012 R2. Post installation I have auto upgraded QuickPatch Project ism file from 2012 to 2019.

It got converted to 2019 with 1 warning and 0 Error. All settings were copied correctly to the upgraded ism file.

Now when I Build(F7) it, it got crash after Extracting COM step for 88 Components and the last updated step in Output log is 
Started signing B352.tmp.........

Have attached the CRASH details.

Before upgrading it to IS 2019 Professional I was able to build ism project without any crash.

Event Viewer Logs below:- 

Faulting application name: isdev.exe, version: 25.0.0.613, time stamp: 0x5cb7a251
Faulting module name: JitV.dll, version: 0.0.0.0, time stamp: 0x5dba9aac
Exception code: 0xc0000005
Fault offset: 0x00008493
Faulting process id: 0xba0
Faulting application start time: 0x01d650562e048b11
Faulting application path: C:\Program Files (x86)\InstallShield\2019\System\isdev.exe
Faulting module path: C:\Program Files (x86)\Microsoft Office\root\Office16\JitV.dll
Report Id: a01f84c3-bc4b-11ea-8170-005056b3173c
Faulting package full name:
Faulting package-relative application ID:

Kindly help me asap. I am stuck.

[Jenifer]

Hi @Amit_pu ,

With the given data it might be difficult to narrow down the problem.Few suggestions:

• Can you try recreate quickpatch with base msi been added to it?If that is not a big deal to do.
• Check the log file for any other errors.
• If nothing helps,please reach out to support with crash .dmp files and project files added to it.

Thanks,

Jenifer

[Amit_pu]

Thanks for the response.

Moving to the suggestions.

1.  I tried building dummy QuickPatch with Basic MSI without having any configuration in it. It got build without any error.

2.  I checked the Log file as well and there is no such error. Log shows the list of activities post triggering of F7 where  it got crash after Extracting COM step for 88 Components and the last 3 lines in Output log are

New Class {D60E967A-4B9B-11D4-80B5-00B0D0119B1C} dynamically acquired for component _8F50CDA2_7D7C_48E3_B6BB_7838F4F33B74_
New Class {D60E967C-4B9B-11D4-80B5-00B0D0119B1C} dynamically acquired for component _8F50CDA2_7D7C_48E3_B6BB_7838F4F33B74_
Started signing B352.tmp.........

(If I compare with old logs of IS 2012, then after New Class {********}  dyanamiacally acquired for component _****_  it fetched New TypeLib COM

New Class {B9E1C00B-C74A-4443-B954-B0011555A344} dynamically acquired for component _FBCD116A_4EF0_4E2C_913A_E8442B64F28F_
New Class {FECC715F-C754-46C9-A82F-1E62CDD3169D} dynamically acquired for component _FBCD116A_4EF0_4E2C_913A_E8442B64F28F_
New TypeLib {A3464CDB-C74E-11D2-9017-00C04F6489AF} dynamically acquired for component _014B26F1_57CC_44B0_9C1B_7D943EED5E4F_
New TypeLib {64950F1C-654F-11D3-BD35-00E0290E10D2} dynamically acquired for component _0AAC0FC4_7F0E_425A_9AD0_2416FC4C125A_)

The above was missing in InstallShield 2019 logs. One more thing there was no Started signing ..... statement in InstallShield 2012 log.

Also to confirm here  Sign the Patch Package under General Information -> Build Settings is unchecked.

So it would be great if it works for you. 

I am not able to find crash dumps specific to this so if you

[Jenifer]

Hi @Amit_pu ,

You could find crash dmp file under [PROGRAMFILESX86]Installshield\2019\System.

Please contact support via support@flexerasoftware.com with the required information like:

1. Version-Installshield 2019 specific version(Eg.R1,R2) 
2. log file -If you could share log file that you had got during build
3. project type-Hopefully it is quick patch

Would be better to share project files with necessary payload to dive into figuring out cause quickly.

Thanks,

Jenifer

[Amit_pu]

Thanks Jenifer.

I will try to reach out to support. In the meanwhile I can share  below details with you.

1.  Version = InstallShield 2019 Professional R2.

2. Log details already shared in this thread before

3. Crash dump - Attached is the the snip of crash dmp file output.

Lets see if you could guess/suggest whats wrong.

[Amit_pu]

Also one more thing, InstallShield 2012 instance still there on my machine.

So Just waana make sure that the problem is not linked with having 2 instance i.e. InstallShield 2012 Professional and InstallShield 2019 Professional R2