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
- :
- Event Viewer (Application) log shows error in ISSetup.dll
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
‎Aug 22, 2012
07:15 AM
Event Viewer (Application) log shows error in ISSetup.dll
Hi
We have used Install scripts projects for our products. This error happens in Windows Vista and Windows 7 OS the installer works fine and runs to completion.
It gives the following error in the application event log (Event Viewer)
Faulting module name: ISSetup.dll, version: 18.0.0.329, time stamp: 0x4e51d640
Exception code: 0xc0000005
Fault offset: 0x000ab43f
Faulting process id: 0xfa8
Faulting application start time: 0x01cd80370eb36430
Faulting application path: C:\User\\AppData\Roaming\\setup.exe
Faulting module path: < C:\User\\AppData\Local\Temp\{GUID}\Disk1\ISSetup.dll >
Report Id: 536f2686-ec2a-11e1-a16e-001321f468f7
How do we fix this error? Does this error cause any problems?
Thanks,
Thananjeyan
We have used Install scripts projects for our products. This error happens in Windows Vista and Windows 7 OS the installer works fine and runs to completion.
It gives the following error in the application event log (Event Viewer)
Faulting module name: ISSetup.dll, version: 18.0.0.329, time stamp: 0x4e51d640
Exception code: 0xc0000005
Fault offset: 0x000ab43f
Faulting process id: 0xfa8
Faulting application start time: 0x01cd80370eb36430
Faulting application path: C:\User\
Faulting module path: < C:\User\
Report Id: 536f2686-ec2a-11e1-a16e-001321f468f7
How do we fix this error? Does this error cause any problems?
Thanks,
Thananjeyan
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 27, 2012
01:46 AM
Hi
Any idea regrading this issue ?
Thanks,
Thananjeyan
Any idea regrading this issue ?
Thanks,
Thananjeyan
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 27, 2012
04:03 PM
Is this behavior occurring with any InstallScript project (built with IS 2012) you try on these machines? For example, if you just create a new InstallScript project, add a file to it, and then build and test again, does a new instance of this error get logged?
If not, you may try commenting out parts of your script for the project(s) that do reproduce this error to isolate where the behavior may be coming from. If commenting out all the script has no effect, then there may be some specific file, registry, or shortcut data causing this behavior (or an object consumed by the project). In any case, the best approach would be to continue to strip parts of the project out until the behavior no longer occurs. If you are able to isolate this down to something specific, we should be able to take a look to see if we can then reproduce the behavior on our end with a set of steps or a sample project that reproduces the behavior.
If not, you may try commenting out parts of your script for the project(s) that do reproduce this error to isolate where the behavior may be coming from. If commenting out all the script has no effect, then there may be some specific file, registry, or shortcut data causing this behavior (or an object consumed by the project). In any case, the best approach would be to continue to strip parts of the project out until the behavior no longer occurs. If you are able to isolate this down to something specific, we should be able to take a look to see if we can then reproduce the behavior on our end with a set of steps or a sample project that reproduces the behavior.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)