View Full Version : Installed InstallShield X now Devstudio 9.0 crashes.

Tim Brown
05-06-2004, 05:22 AM

I made the mistake of installing ISX onto the same machine as DevStudio 9 and so now I cannot build my project in DevStudio.

I get this error.....

Exception ACCESS_VIOLATION (0xc0000005)
at address 0x07583544 trying to read address 0x075ce7d8.

File : C:\Program Files\InstallShield\DevStudio 9\System\isdev.exe
Version :
Exception : c0000005
Address : 07583544
Access Type : read
Access Address : 075ce7d8

Registers : EAX=075ce7d8 CS=001b EIP=07583544 EFLGS=00010206
: EBX=00000001 SS=0023 ESP=0012d664 EBP=0012d6a4
: ECX=00000005 DS=0023 ESI=075b3f64 FS=003b
: EDX=77fcf190 ES=0023 EDI=00000001 GS=0000

Stack Trace : 77f85058 77f8f87e 77e9cfb1 075f402b
: 075fa87e 0012dbb8 78010362 0042956f
: 77e9ca90 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000

I think it's something to do with the merge modules for the MFC 7.1 runtime or XML 4.0

David Thornley
05-06-2004, 11:34 AM

I'm sorry you had to run into this. We have determined that the InstallScript objects are conflicting with each other. We are looking into fixing this, but in the meantime you can get the Dev9 build working again by self-registering the object wizards in the ObjectsPro folder of the InstallShield 10 installation.

Tim Brown
05-07-2004, 03:31 AM

Thanks for the quick reply.
I may be particularly stupid but I cannot see what I have to self register.
My ObjectPro folder contains a lot of sub folders containing InstallShield projects. Do I have to build and install each one?

Or is the best plan to uninstall InstallShield 10 and re-install DevStudio 9.0 + SP1 etc. etc. and forget about IS10 until you fix it.

Thanks Tim.

05-07-2004, 10:31 AM
The problem is the classid's and typelibs were not changed for the wizards. The wizards are COM objects. The problem is the last install you did registers the wizards with the paths to the wizard files it installs.

What's happening is once you install X it registers the MergeModuleObj.dll file to a path like below.

InstallShield X\ObjectsPro\Merge Module Object\MergeModuleObj.dll

Now when you launch DevStduio 9 and use the Merge Module Object, it's using the InstallShield X wizard.

The file MergeModuleObj.dll has changed a little bit to support installing the Msi engines. That's why it's crashing. It's trying to read object properties that are not in 9. It's throwing an exception and then a subsequent crash.

Unofrtunately, this is not just a problem with this one object, but all objects. All your objects' wizards are registered to the InstallShield X location, since it was installed last.

The only objects wizards that have changed are the Merge Module Holder Object and the Windows Mobile (formerly CE) object. The other wizards have not so it's not a big deal.

So if you are to use 9, you must re-register the file "ObjectsPro\Merge Module Object\MergeModuleObj.dll" located where you installed DevStudio 9.

If you were to go back and use InstallShield X, you would have to register this file in the directory where InstallShield X is installed.

The above two sentences really only apply if you are using the object.

Another problem you will see if you uninstall one (either 9 or X) is that you will lose all object wizards. Because the uninstall will unregsiter the wizards dll's when it uninstalls them. Hence no classid in the registry. The easiest thing to do would be to repair the product you did not uninstall.

I know the above is a lot of information, but I wanted to give a full picture of what the problem is. It's really an "easy" problem (I am not trying to make light of the seriousness of the problem) once you know what's going on, but very frustrating if you don't.

Sorry for the inconvenience--I am probably somewhat responsible for this.


Tim Brown
05-07-2004, 10:52 AM
Hi Kent,

Thanks for the reply, far too much to understand on a Friday afternoon :-)
I hate to ask, but why did no one spot this before the product shipped.

I guess to be safe, in case anything else in ISX breaks Dev9.
I should uninstall all Installshield products, then re-install Professional 7, DevStudio9 the service Packs, the objects, and the standalone builds (7 and 9).

Then find a separate PC to use ISX on.


05-07-2004, 12:35 PM
You shouldn't need to worry about any other conflicts besides the Pro Object wizards. These are the only files we use COM. For other activex controls we don't use traditional COM--no reg entries.

However, it's probably best to install InstallShield X on another machine for now.

As far as your question, I guess we thought we had co-existence "licked". As it turns out we did for everything except Pro Objects. Honestly, this Pro Object thing is really an inexplicable oversight.

I think you will find the new Merge Module Holder Object is more robust with its built-in support for installing the Msi engines.

I have made some more improvements (probably more transparent for setup authors like yourself, though) for the next release--SP, perhaps.


Tony Dixon
05-10-2004, 07:10 AM
I get a smiler problem, that i have Installsheild X install on my system ( in a diffent location to version 9).

The debugger no longer works.

I press the debug button on the tool bar and the setup start to install, not debug window is shown and the install continues as if you press run.:confused:

Tim Brown
05-10-2004, 09:41 AM
Hi Tony,

Yes me too, I got round it by uninstalling ISX and DevStudio and then putting DevStudio back on again.
I guess for the moment I'm going to need another PC or partition the test ISX on.


05-12-2004, 05:36 PM

Regarding the debugger problem, this is know a known issue, with the tracking #1-NHAHE, it is currently scheduled to be fixed for the first InstallShield X service pack.

As a workaround, to fix the problem you need to register the appropriate debugger before attempting to debug a setup built with that version. (i.e.)

To debug Dev9 setups:

1. Go to the <Dev9 Install Location>\System folder and run "ISDbg.exe" or "ISDbgCnv.exe" (ISMSI setups) with the command line /REGSERVER.

You can then debug Dev9 setups.

If you then want to debug IS X setups you will need to register the InstallShield X "ISDbg.exe" or "ISDbgCnv.exe", as currently only one of the these debuggers can be registered on the system at a time.

Devin Ellingson
InstallShield Software Corporation

Tim Brown
05-13-2004, 06:52 AM
Hi Devin,

Thanks for the reply.
Are there any other COM registered parts of the applications which are also broken or have we managed to find the only two bits ?

Or in other words are there any other known problems which we should know about :)

Thanks Tim.

Tim Brown
07-22-2004, 11:45 AM

I see that Service Pack 1 for InstallShield X has arrived and according to the readme information on the web site both of the problems described in this thread have been fixed.

If I now install the InstallShield X from the CD and then install Service Pack 1, will DevStudio still work.
That is to say, does Service Pack 1 put DevStudio back together again, or is the installation process needed to get both products working more complex than that?

Thanks Tim.

07-26-2004, 12:58 PM
After I installed sp1 I started getting an error much like your build error whe trying to build my ISX project.