Symantec VSS Provider conflicting with VSS Backups Error creating volume snapshot(s): VSS_E_OBJECT_NOT_FOUND (4045920)

There can be several factors why a backup that utilizes VSS will fail.

Some common errors are:

• Snapshots already existing
• Space (resources) in the temp directory or working directory where snapshots are being created
• Permissions
• VSS component(s) errors such as Writer, List, Create....(basically any part of its services)
• Other VSS related applications running causing conflict with eachother
• Other VSS providers other than the MS VSS provider running

The basis for this solution is in regards to the Symantec VSS Provider or the Symantex Symsnap VSS Provider.

This service disables the Windows Native MS VSS Provider and runs its own VSS Provider

When the Symantec Symsnap service is run while a NV Backup using VSS is trying to run, the backup will fail with:

Error 2012/01/19 10:01:02 648 Data Plugin SERVER1 Error creating volume snapshot(s): VSS_E_OBJECT_NOT_FOUND
Error 2012/01/19 10:01:02 648 Data Plugin SERVER1 Failed to create VSS snapshot

Disable the following to Symantec services -

** SymSnapService

**Symantec SymSnap VSS Provider

Once these are disabled, follow the below steps to remove the Symantec provider from the list of providers and re-enable Microsofts Volume Shadow Service:

1. Open Regedit
2. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\
3. Expand Providers and you should see three keys: Enum, and two GUID's (Long strings of letters and numbers).
4. Click on the top GUID in the list and in the right-hand pane the Default string should have the name of the Symantec provider. If not check the other GUID.
5. Once you find the right GUID export the whole GUID and save it somewhere safe.
6. Delete the Symantec provider GUID and close the registry
7. Open Windows services and Restart the "Volume Shadow Copy" service. It may be stopped to begin with, that's okay.
8. Check and see if the provider is gone from: vssadmin list providers
9. Reboot the server when next possible. (Not Neccesary)