Re-register Microsoft VSS – Failed Backups

Recently, I had a Windows 2008 R2 server, running Backup Exec, that was constantly failing during snapshot processing backing up the system state. The backups would show the following error:

AOFO: Initialization failure on: "System$State". Advanced
Open File Option used: Microsoft Volume Shadow Copy
Service (VSS).
V-79-10000-11226 - VSS Snapshot error. The Microsoft
Volume Shadow Copy Service (VSS) snapshot provider
selected returned: "Unexpected provider error". Ensure
that all provider services are enabled and can be started.
Check the Windows Event Viewer for details.

Also, the service “Volume Shadow Copy”, which is set to manual, would be in a stopped state.  In the windows application event log, I found event ID 12293:

Volume Shadow Copy Service error: Error calling a
routine on a Shadow Copy Provider
{b5946137-7b9f-4925-af80-51abd60b20d5}. Routine
details EndPrepareSnapshots
[hr = 0x80042302, A Volume Shadow Copy Service
component encountered an unexpected error.

At my command prompt, I made sure that Microsoft VSS was the only provider: “vssadmin list provers”
And also checked the status of the VSS writers, which some were in error states: “vssadmin list writers”

Because Symantec could easily blame Microsoft, and Microsoft blame Symantec: it is recommended to run Windows Backup to backup the system state and see if it fails.  If it does not fail, then Symantec is to blame. If it does fail (like mine did), then Microsoft Windows has a problem.  To run a system state backup in 2008 R2, open an elevated command prompt and type: (F: being the volume location to backup to)

wbadmin start systemstatebackup -backupTarget:F: -quiet

At this point, since my backup failed, VSS was to blame. So, the final step is to re-register VSS. To do so, (in 2008) copy the following into a .bat file and run, then reboot.

net stop "System Event Notification Service"
net stop "Background Intelligent Transfer Service"
net stop "COM+ Event System"
net stop "Microsoft Software Shadow Copy Provider"
net stop "Volume Shadow Copy"
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ATL.DLL
regsvr32 /s comsvcs.DLL
regsvr32 /s credui.DLL
regsvr32 /s CRYPTNET.DLL
regsvr32 /s CRYPTUI.DLL
regsvr32 /s dhcpqec.DLL
regsvr32 /s dssenh.DLL
regsvr32 /s eapqec.DLL
regsvr32 /s esscli.DLL
regsvr32 /s FastProx.DLL
regsvr32 /s FirewallAPI.DLL
regsvr32 /s kmsvc.DLL
regsvr32 /s lsmproxy.DLL
regsvr32 /s MSCTF.DLL
regsvr32 /s msi.DLL
regsvr32 /s msxml3.DLL
regsvr32 /s ncprov.DLL
regsvr32 /s ole32.DLL
regsvr32 /s OLEACC.DLL
regsvr32 /s OLEAUT32.DLL
regsvr32 /s PROPSYS.DLL
regsvr32 /s QAgent.DLL
regsvr32 /s qagentrt.DLL
regsvr32 /s QUtil.DLL
regsvr32 /s raschap.DLL
regsvr32 /s RASQEC.DLL
regsvr32 /s rastls.DLL
regsvr32 /s repdrvfs.DLL
regsvr32 /s RPCRT4.DLL
regsvr32 /s rsaenh.DLL
regsvr32 /s SHELL32.DLL  
regsvr32 /s shsvcs.DLL
regsvr32 /s /i swprv.DLL
regsvr32 /s tschannel.DLL
regsvr32 /s USERENV.DLL
regsvr32 /s vss_ps.DLL
regsvr32 /s wbemcons.DLL
regsvr32 /s wbemcore.DLL
regsvr32 /s wbemess.DLL
regsvr32 /s wbemsvc.DLL
regsvr32 /s WINHTTP.DLL
regsvr32 /s WINTRUST.DLL
regsvr32 /s wmiprvsd.DLL
regsvr32 /s wmisvc.DLL
regsvr32 /s wmiutils.DLL
regsvr32 /s wuaueng.DLL
sfc /SCANFILE=%windir%\system32\catsrv.DLL
sfc /SCANFILE=%windir%\system32\catsrvut.DLL
sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL
net start "COM+ Event System"

At this point, I rebooted, and then ran another test backup.  The VSS service stayed running, and the backup completed successfully.

Tags: , , ,

One Response to “Re-register Microsoft VSS – Failed Backups”

  • Ruan says:

    Thanks man, this post helped me allot! Was struggling with this for some time. Actually looking at getting away from Symantec’s product, was better when Veritas was running thing IMO. have you played around with DataProtection Manager at all ?

Leave a Comment

2013 | 2014 | 2015 | 2016


Voted Top 100 vBlog 2016