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
- :
- Access Violation with IS2013
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
Apr 07, 2014
03:24 AM
Access Violation errors with Installshield setup
My project is migrated from 2012 to 2013 premier. When I made the setup and installed, on couple of Client laptops it is giving Access Violation related crashes.
My code base in VS2010. When I copy the binaries(i.e. the dlls and the exe's) directly to the client pc it works. No crashes.
But same binaries deployed through Installshield setup is giving lots of crashes. All related to Access Violation "Attempted to read or write protected memory. This is often indication that memory
is corrupt". Usually the crashes are for imm32, ole32, shwapi, mswsock
One observation : there is some software called Glary's Utilities installed and looks like laptop image is encrypted.
I am not sure what is causing this issue. My binaries looks fine.
Please help me out in resolving out this issue.
My code base in VS2010. When I copy the binaries(i.e. the dlls and the exe's) directly to the client pc it works. No crashes.
But same binaries deployed through Installshield setup is giving lots of crashes. All related to Access Violation "Attempted to read or write protected memory. This is often indication that memory
is corrupt". Usually the crashes are for imm32, ole32, shwapi, mswsock
One observation : there is some software called Glary's Utilities installed and looks like laptop image is encrypted.
I am not sure what is causing this issue. My binaries looks fine.
Please help me out in resolving out this issue.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 28, 2014
11:58 AM
Our tech support has reported this issue for several customers. While it hasn't worked for all of them, some reported success after the customer disabled Bitlocker on the machine where it was failing.