Problems with VSS

[tynana]

Before I start the query, let me tell you about my setup. It is SBS 2003 Premium running with MS Exchange, ISA 2004, SQL, WSUS, Norton Antivirus, 2 NICs and a router, dynamic IP, DDNS service from dyndns.org. Now the reason I’m here is we were facing some problems from past couple of days with Symantec Backup Exec which we managed to fix completely 2 days with the help of Symantec customer support.

But the problem is we are still getting some errors related to the same in Event Viewer log. I think Symantec Backup Exec issue was somehow connected to VSS. Since yesterday we are actually using NTBackup for individual mailboxes, but VSS is causing failures. I don’t understand what could be the reason.

Here is the event log, hope anyone from you can help me with this:
8193 - Volume Shadow Copy Service error: Unexpected error calling routine
CoCreateInstance. hr = 0x80070057.

11 - Volume Shadow Copy Service information: The COM Server with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and name VSSEvent cannot be started. [0x80070057]
20 - Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy
provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80040154].

Please help.

[Brandy]

I found very good article describing the problems under error code 8193. The article is from BE tech support and am sure it will surely help you out. So just check this: http://eventid.net/display.asp?event...ce=VSS&phase=1. They have also provided some patches for the VSS error.

[tynana]

Thank you very much for the help Brandy. I followed that article, in start it was bit annoying because the solution was only visible after becoming their subscriber but it was very helpful. The problem is now fixed and everything working fine. Appreciated.

[prmiller]

I have the exact same problems as outlined in this article. Can you please share specifically what you did to resolve the issue.