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
- :
- Re: Crash when building InstallScript 2011 project using 2014
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
‎Oct 06, 2014
01:06 PM
Crash when building InstallScript 2011 project using 2014
I have been tasked to investigate upgrading our IS 2011 project to 2014 - my company has licenses for versions back to 2008 or so.
When I upgrade and build the project using 2014, the IS IDE crashes with the following during the "Checking string table references..." step:
Exception ACCESS_VIOLATION (0xc0000005)
at address 0x7042aa58 trying to read address 0x00000008.
File : C:\Program Files (x86)\InstallShield\2014\System\isdev.exe
Version : 21.0.0.289
Exception : c0000005
Address : 7042aa58
Access Type : read
Access Address : 00000008
Registers : EAX=0018d038 CS=0023 EIP=7042aa58 EFLGS=00010202
: EBX=00000000 SS=002b ESP=0018cf58 EBP=0018cfa8
: ECX=703c4834 DS=002b ESI=00000000 FS=0053
: EDX=009c9038 ES=002b EDI=0018d028 GS=002b
Stack Trace : 75352070 753b6c2f 0fbe4628 0fbe4840
: 0fbfd5dd 0fbcf4f6 0fbced42 0fbced3b
: 0fbced3b 0fbcf5dd 0fbd043d 0fc005d8
: 0fc00533 04a13e4d 04a1374f 04a2a00d
: 02341b6d 02341244 0237406d 023804b9
: 04441c2b 04ac69ce 049588b6 04959d77
: 07507e48 075056d7 074d5a07 074d6b7b
: 110158b1 1102c7d0 02872a26 0042bfbc
The project builds just fine using IS 2011 and 2012.
Clues?
Bo
When I upgrade and build the project using 2014, the IS IDE crashes with the following during the "Checking string table references..." step:
Exception ACCESS_VIOLATION (0xc0000005)
at address 0x7042aa58 trying to read address 0x00000008.
File : C:\Program Files (x86)\InstallShield\2014\System\isdev.exe
Version : 21.0.0.289
Exception : c0000005
Address : 7042aa58
Access Type : read
Access Address : 00000008
Registers : EAX=0018d038 CS=0023 EIP=7042aa58 EFLGS=00010202
: EBX=00000000 SS=002b ESP=0018cf58 EBP=0018cfa8
: ECX=703c4834 DS=002b ESI=00000000 FS=0053
: EDX=009c9038 ES=002b EDI=0018d028 GS=002b
Stack Trace : 75352070 753b6c2f 0fbe4628 0fbe4840
: 0fbfd5dd 0fbcf4f6 0fbced42 0fbced3b
: 0fbced3b 0fbcf5dd 0fbd043d 0fc005d8
: 0fc00533 04a13e4d 04a1374f 04a2a00d
: 02341b6d 02341244 0237406d 023804b9
: 04441c2b 04ac69ce 049588b6 04959d77
: 07507e48 075056d7 074d5a07 074d6b7b
: 110158b1 1102c7d0 02872a26 0042bfbc
The project builds just fine using IS 2011 and 2012.
Clues?
Bo
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 07, 2014
01:53 PM
There should likely be a .dmp file in your InstallShield system folder for each of these crashes. That can often help us track down the exact cause of the crash. It would be best if you can open a support case on your maintenance plan, in case other files need to be exchanged, but if you post it here we might be able to take a look.
(Note that some .dmp files include memory information from the process, so some care may be necessary with the file if it may have privileged information such as certificate passwords. The .dmp files we generate on crash shouldn't have much if any memory information included.)
(Note that some .dmp files include memory information from the process, so some care may be necessary with the file if it may have privileged information such as certificate passwords. The .dmp files we generate on crash shouldn't have much if any memory information included.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 09, 2014
01:05 PM
MichaelU wrote:
Your crash appears to match the symptoms of IOJ-1662589. We have a hotfix for this available; to install it, back up ISWIScanners.dll from your InstallShield\2014\System folder, and extract and put the attached file in its place.
That solved the crash, Michael. Many thanks!
I'll pass this on to my corporate contact.
Bo