VSS Shadow Copy Error and Damaged Com+ Catalog

[Steph]

I have been working on a compuer that began having difficulty several weeks ago. It was either started by or made worse by an incomplete removal and then a reinstall of Norton AntiVirus 2003. It is now getting volume shadow errors (no NTFS partition or drive) and also the damaged com+ catalog errors. I have done a system restore and also done a repair of the installation from the XP pro CD. We cannot create an ASR recovery backup because each time you try to backup the system state data this com+ error causes the backup to fail.

I have checked to be sure the com+ event system service and com+ system application services are set to manual and also run the "reg query hklm\system\setup" command and there are no errors. The value for each key is set to 0. I have followed the instructions for "How to Clean up a Damaned Com+ Catalog", knowledge base article #315296. This works well until you start the install through add/remove programs for windows components. You see it start to rebuild the com+ system and then it fails with the following error: "Com+ raised an exception while procession OC_Complete_Installation setup d:\nt\com\com1x\src\complussetupcomsetup\ccomplusxxx.cpp* line 565, Error Code=0x80040206, An unexpected internal error was deteched. The com+ event classes could not be registered." *The very last ccomplusxxx.cpp might not be quite correct as I can't read my writing in my notes but it is close, sorry! Anyway, after this error, the installation completes and everything is fine but the original com+ backup problem remains as before the component install was tried.

Is there anything else I am missing to try with the exception of formatting the drive and reloading? This particular computer belongs to a business running a proprietary software package they are not sure can be reloaded onsite with the software available. Usually, the company dials in to help install and they may not be available for several days and it is mission critical so I would prefer not to have to try to reload it. Also, if I complete a new install without formatting the drive, will it see the existing software and pull it into the registry? I have never known this to be the case but have been told it works and I am skeptical since there would be a new registry built with the install. I do have a backup of the current registry.

Thanks!
Steph

[Adi Oltean [MSFT]]

Hi Steph,

Reformatting everything and performing a clean install should be the
last chance solution. Still, before trying that, I would suggest you
to contact the Microsoft Product Support - they might be able to help
you here. If this turns out to be a bug in Microsoft software then you
do not even have to pay for support.

BTW - before going to PSS or reformatting the machine can you try one
more thing?

1) Make sure that you see the OLE32.DLL file in %windir%\system32

2) Run the command:
REGSVR32 ole32.dll

3) Retry repairing the COM+ catalog as you mentioned below.

Thanks, Adi

P.S. This posting is provided "AS IS" with no warranties, and confers
no rights.

"Steph" <anon...@discussions.microsoft.com> wrote in message news:<DAB204AA-A369-4556...@microsoft.com>...

[Ivaylo Mutafchiev]

Adi,

thank you very much for a valuable suggestion. I've been searching the
google & groups for days trying to find out what is wrong with my
installation. The behaviour was similar as Steph describes. Following a
suggestion in a MS knowledge base note I tried to reinstall COM+ on my WinXP
Pro at Compaq laptop. Why? It looks like IIS was broken and asp were not
displayed. Also when I tried to open a component services at my computer -
the application exits without any warning.
Further re-installation of the COM+ fails with the message:
~~~~~~~~~~~~~
Sub-component COM+ raised an exception while processing the
OC_COMPLETE_INSTALLATION setup message.
d:\nt\com\com1x\src\complussetup\comsetup\ccompluscore.cpp (line 565)

Error Code = 0x80040155

Interface not registered
The COM+ event classes could not be registered.
~~~~~~~~~~~~~

According to the comsetup.log I started to search the web and found loans of
similar postings and allmost everybody suggests re-installing XP (which is
not an option in my case).

The only thing I did more than suggested in a knowledge base note was to
re-register ole32.dll in a way you mentioned:
REGSVR32 ole32.dll

After that COM+ re-installation passed successfuly, and after re-installing
IIS my web-server serves asp-pages again.

Thank you.

--
Ivaylo Mutafchiev
SAP R/3 Dept - BC consultant
Petrol Holding
Varna, Bulgaria

"Adi Oltean [MSFT]" <aol...@microsoft.com> wrote in message
news:151ad89d.04022...@posting.google.com...