Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

System State backup fails

Created: 14 Jun 2013 • Updated: 18 Jun 2013 | 3 comments
This issue has been solved. See solution.

Hello...I am getting error when backing up the System State on a domain controller. (Windows Server 2003)

The job log error is:

V-79-57344-34086 - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008526): Backup Exec could not locate a Microsoft Volume Shadow Copy Services (VSS) software or hardware snapshot technology for this job. Select a valid VSS snapshot technology for the target computer.

Check the Windows Event Viewer for details.

And the event viewer on the domain controller  does show 2 VSS errors.

1)   Volume Shadow Copy Service error. Unexpected error calling routing CoCreateInstance. hr =0x80070057

       Event ID: 8193   Source: VSS

2)  Volume Shadow Copy Service information: The COM Server with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e] and name VSSEvent cannot be started.[0x80070057]

I have tried 2 things as shown in the following URLS

http://support.microsoft.com/kb/940184    No joy

http://support.microsoft.com/kb/2009533   No joy

Any idea is appreciated!

Comments 3 CommentsJump to latest comment

lmosla's picture

Hello,

Was this an upgrade or fresh install of BE 2012?  Try deleting the job and then recreate it.

Also see this document http://www.symantec.com/business/support/index?page=content&id=TECH56448

pkh's picture

Edit your job and specifically specify VSS in AOF.  See the screenshot below

BE 2012 - AOF, use MS provider.png

JustTryinToGetItToWork's picture

Interestingly, when I re-registered the dll's as indicated in a previously posted link, and I got errors like "unspecified module could not be found" on 3 of them.

I ended up rebooting the server and now the vssadmin list writes command did populate properly on the server.

NTBackup also worked on the Server.

And BackupExec also then backed up successfully.

Thank you for your input!

SOLUTION