Repairing a corrupted COM database.

By mdfreeman ·
We have a Windows Server 2003 system, we are using NTBackup for our system backups...these backups are failing. The backup report is as follows:

Backup Status
Operation: Backup
Active backup destination: File
Media name: "Temp Thursday Backup.bkf created 6/11/2010 at 8:36 AM"

Volume shadow copy creation: Attempt 1.
Timeout before function completed

Error returned while creating the volume shadow copy:0xffffffff.

Error returned while creating the volume shadow copy:ffffffff
Aborting Backup.


The operation did not successfully complete.


Additionally, two events are created in the Application log:
Event I 20
Source: VSS

Event I 8193
Source: VSS

Event ID 20 flat out says that the COM+ database is corrupt, event ID 8193 indicates a problem with the COM+ infrastructure.

I have the procedure to repair a corrupted COM+ catalog (re-registering several dll's, deleting the COM3 registry key, renaming clbcatq.dll and reinstalling COM+); my question is...might following this procedure affect programs installed on the server, i.e. Kerio Mailserver, Symantec Corporate, etc?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -


by ---TK--- In reply to Repairing a corrupted COM ...

Well, it currently doesn't work... So re-registering a whole mess of .dll's isn't really going to hurt... Worst case it still doesn't work.

In my experience, repairing the COM+ works half the time. The other half ended up in a rebuild & restore from backups.

Best of luck!

Collapse -


by mdfreeman In reply to opinion....

Thanks for the voice of experience, this is the first time I've had to deal with this. I guess I'll let my client know that we may have to do a restore. Any suggestions on how I may be able to get a backup to run in case I have to do a restore? Unfortunately, I just took this server over from another individual and there has not been a valid backup in over two weeks.

Related Discussions

Related Forums