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
- :
- ISE2011 IDE Crash
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
‎Jul 14, 2011
08:38 AM
ISE2011 IDE Crash
I used ISE2011 about 2 weeks ago on this computer (Win7 Ultimate x64) and everything was fine. I went to use it today and everytime I click on a file to add it to the build ISE crashes. In my attachment you can see the file I clicked on (and it doesnt matter what I click on) as well as the error message. Any ideas on this? I cant even use ISE right now because I cannot add any files to my build...
I am using ISE 2011 Hotfix A
Also Mods: I just realized I posted this in the wrong section, move if necessary please. 😮
I am using ISE 2011 Hotfix A
Also Mods: I just realized I posted this in the wrong section, move if necessary please. 😮
(19) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2011
09:11 AM
If InstallShield doesn't violently crash with the MS VC++ error I noted in this thread, http://community.flexerasoftware.com/showthread.php?t=198162, I get the message you're getting, but at start-up.
If you go to your IS installation directory, %PROGRAMFILES%\InstallShield\2011, is there an iside.log file, and does it also have the lines:
C:\CodeBases\isdev\src\FrontEnd\Views\IsWsInstallScripts\ScriptEditorWnd.cpp 1359: Out of memory.
Maybe some kind of relation to my post, just speculating.
If you go to your IS installation directory, %PROGRAMFILES%\InstallShield\2011, is there an iside.log file, and does it also have the lines:
C:\CodeBases\isdev\src\FrontEnd\Views\IsWsInstallScripts\ScriptEditorWnd.cpp 1359: Out of memory.
Maybe some kind of relation to my post, just speculating.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2011
09:16 AM
mpa109 wrote:
If InstallShield doesn't violently crash with the MS VC++ error I noted in this thread, http://community.flexerasoftware.com/showthread.php?t=198162, I get the message you're getting, but at start-up.
If you go to your IS installation directory, %PROGRAMFILES%\InstallShield\2011, is there an iside.log file, and does it also have the lines:
C:\CodeBases\isdev\src\FrontEnd\Views\IsWsInstallScripts\ScriptEditorWnd.cpp 1359: Out of memory.
Maybe some kind of relation to my post, just speculating.
I dont have that file in C:\Program Files (x86)\InstallShield\2011
also another screen shot of the error info.
and the full error text
Unknown exception.
File : C:\Program Files (x86)\InstallShield\2011\System\isdev.exe
Version : 17.0.0.714
Exception : c015000f
Address : 77eb45c1
Access Type :
Access Address : 00000000
Registers : EAX=0018fcfc CS=0023 EIP=77eb45c1 EFLGS=00000202
: EBX=11b25ac6 SS=002b ESP=0018fcf0 EBP=0018fd4c
: ECX=00000004 DS=002b ESI=00983d38 FS=0053
: EDX=00000000 ES=002b EDI=00983e28 GS=002b
Stack Trace : 76425454 69a482cd 755962fa 75596d3a
: 755977c4 7559788a 69e6e3c0 69e3af1a
: 00466211 7642339a 77e69ed2 77e69ea5
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2011
09:18 AM
I replied but it didnt show 😞
No I dont have that file...
Here is another screen and the actual error text
No I dont have that file...
Here is another screen and the actual error text
Unknown exception.
File : C:\Program Files (x86)\InstallShield\2011\System\isdev.exe
Version : 17.0.0.714
Exception : c015000f
Address : 77eb45c1
Access Type :
Access Address : 00000000
Registers : EAX=0018fcfc CS=0023 EIP=77eb45c1 EFLGS=00000202
: EBX=11b25ac6 SS=002b ESP=0018fcf0 EBP=0018fd4c
: ECX=00000004 DS=002b ESI=00983d38 FS=0053
: EDX=00000000 ES=002b EDI=00983e28 GS=002b
Stack Trace : 76425454 69a482cd 755962fa 75596d3a
: 755977c4 7559788a 69e6e3c0 69e3af1a
: 00466211 7642339a 77e69ed2 77e69ea5
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2011
09:39 AM
I have a similar error. Everytime I exit install shield I get the same dialog box the the application has to close and restart.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2011
09:44 AM
I guess I am glad I am not the only one, but is there a fix or a solution to this issue??
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2011
05:03 PM
Regarding the original poster's issue, have you installed any software that registered new shell extensions on this machine? The source file list is an Explorer control (right-click a file and notice the context menu is the same as in Windows Explorer) and as such shell extensions will be loaded into the InstallShield IDE process when that control is loaded or interacted with. If a new shell extension is doing something it shouldn't be and causing a crash, this will cause the InstallShield IDE to crash.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 18, 2011
04:53 PM
You may try repairing or reinstalling InstallShield. If this doesn't resolve the behavior, there is likely something else on the machine that has changed that is causing the behavior you are seeing in the source file list, especially if it was working at some point before.
Being able to debug this issue further will likely require a way of reproducing this scenario in house such that we can attach a debugger to the IDE process and try to determine where it is crashing (unfortunately, the crash dump that InstallShield lists does not include a list of modules loaded in the process which is needed for at least isolating where the faulting instruction was).
Being able to debug this issue further will likely require a way of reproducing this scenario in house such that we can attach a debugger to the IDE process and try to determine where it is crashing (unfortunately, the crash dump that InstallShield lists does not include a list of modules loaded in the process which is needed for at least isolating where the faulting instruction was).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 19, 2011
08:15 AM
joshstechnij wrote:
You may try repairing or reinstalling InstallShield. If this doesn't resolve the behavior, there is likely something else on the machine that has changed that is causing the behavior you are seeing in the source file list, especially if it was working at some point before.
Being able to debug this issue further will likely require a way of reproducing this scenario in house such that we can attach a debugger to the IDE process and try to determine where it is crashing (unfortunately, the crash dump that InstallShield lists does not include a list of modules loaded in the process which is needed for at least isolating where the faulting instruction was).
Ok, so I have Hotfix A installed and I cannot do I repair because I do not have the MSI file. Where can I obtain what I need to do the repair??
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 19, 2011
02:09 PM
You should be able to run a repair from the InstallShield entry in Add/Remove Programs. Hotfix A is a patch that will be reinstalled with the repair.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 19, 2011
02:15 PM
Ya... not so much.
I tried that and it just asks for the CD and then says that the CD doesnt have the correct MSI with Hotfix A.
I tried that and it just asks for the CD and then says that the CD doesnt have the correct MSI with Hotfix A.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 19, 2011
03:13 PM
Windows Installer should reject an MSI package on a prompt for source only if the package code of the registered MSI and the selected MSI don't match (assuming the product code and package name haven't changed). Since we didn't release Hotfix A as an MSI, there should be no way of encountering this scenario.
It is possible that you are seeing the results of an issue with MSI source resolution on platforms that support UAC.
Please try running the repair from the original installation media (setup.exe). If this still prompts for source, run the setup.exe with administrator privileges and this may resolve the behavior you are seeing.
It is possible that you are seeing the results of an issue with MSI source resolution on platforms that support UAC.
Please try running the repair from the original installation media (setup.exe). If this still prompts for source, run the setup.exe with administrator privileges and this may resolve the behavior you are seeing.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 20, 2011
08:12 AM
Ok so I tried doing the repair starting from the setup.exe. I tried it with out running as Admin, that did not work. I tried it running as admin and that didnt work either. I really need to get this project built at this point, so any more suggestions?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 21, 2011
02:32 PM
The product can be uninstalled and reinstalled. Unfortunately, we have not encountered this repair behavior in the past with IS 2011 and Hotfix A installed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 26, 2011
10:56 AM
joshstechnij wrote:
The product can be uninstalled and reinstalled. Unfortunately, we have not encountered this repair behavior in the past with IS 2011 and Hotfix A installed.
Yes I did that and that as well failed, since I couldn't find a solution and Flexera has not been a lot of help.... I solved this issue myself. For future people who find this post: Just find another piece of software, that's what I did and it solved my issues and I got a better end all solution for less money.
Though I should note that this was aggrivating before all of this ISE2011 was working pretty well for what we needed, but since the issue couldnt be solved we moved on. :mad: :mad: 😞
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
11:52 AM
As a point of future reference, we were able to reproduce this behavior in house by enabling the Windows accessibility narrator. When this is enabled, on selection of an item in the source files list view, Windows sends messages to list view type controls in a slightly different way than ordinary, and the code we have to handle one of these notification requests does not correctly handle the message (unfortunately this has been this way for a while and could occur with most versions of InstallShield on any Windows version that sends messages in this unexpected manner). Due to another issue with how structured exception handling works in the operating system on x64 versions of Windows, the original exception that occurs disappears and the process is allowed to continue running. This leaves the process in an unstable state and eventually results in a completely unrelated crash, making this scenario quite difficult to track down.
Note that there may be other triggers of this particular behavior. It is possible that other screen reader utilities, automated UI test utilities, or other applications that request data from a list view in individual parts will result in InstallShield crashing while displaying or selecting items in the Files and Folders source file list. Temporarily disabling these should allow for working around the behavior.
This particular issue will be resolved in the next release of InstallShield.
Note that there may be other triggers of this particular behavior. It is possible that other screen reader utilities, automated UI test utilities, or other applications that request data from a list view in individual parts will result in InstallShield crashing while displaying or selecting items in the Files and Folders source file list. Temporarily disabling these should allow for working around the behavior.
This particular issue will be resolved in the next release of InstallShield.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 20, 2012
09:25 AM
I am seeing the exact same behavior as described in the above post. How can I resolve this?
Thanks,
Taulbee S Davis
Thanks,
Taulbee S Davis
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 18, 2012
01:00 PM
I am experiencing the same error with Installshield Express 10, please tell me what the fix is for this error?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 20, 2012
02:21 AM
here is the link that may help you
http://social.msdn.microsoft.com/Forums/en-US/sqlce/thread/8e48b5f0-066e-43b4-8a0e-2fdcd52670a9/
http://social.msdn.microsoft.com/Forums/en-US/sqlce/thread/8e48b5f0-066e-43b4-8a0e-2fdcd52670a9/
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)