1 reply to this topic

[Ballano Gris]

I have a customer getting this message ( Catastrophic failure) on one of their Win NT machines..

I found the solution below in a usenet article, but before I have a customer noodle around in their registry, I want to see if anyone else has seen or solved this.

Anyone?
-------------------------------------------------------------------

See

http://groups.google...e...al&start=25

for the start of this thread. I fixed my Win2K problem with
InstallShield installers crashing. For some reason, I had a dud
registry entry:

====
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}]
@="PSDispatch"

[HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer]
@="ole2disp.dll"

[HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32]
@="oleaut32.dll"
"ThreadingModel"="Both"
"InprocServer32"="Dmi?y'%,g(V$DC!{,`WjOLE_Automation_Support>M5KDYSUnf(HA*L[xeX)y[~]qsL+$_T(g(yqBefePAr^Main>M5KDYSUnf(HA*L[xeX)y"
====
Deleting the bogus "InprocServer32" key from
"[HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32]"
and rebooting fixed the problem. I don't know what caused this dud
registry entry to be created, but for some reason it kills
InstallShield 6.31 installers stone dead. I hope this can help anyone
else who has this problem.

Oh, how did I locate this problem? I used the Win2K "Registry
Monitor" to log the accesses to the registry, and checked out the last
thing that "Setup.exe" did before it crashed.

Cheers,

[Taco Bell]

So the IS setup fails to even start? 'cause if that's the case, I now always work through this IS Knowledge Base article to try and fix the problem.

However, I've never encountered this specific issue.