VSS Errors 11, 8193, 12289, 12292 and 12302 Looking at the Application Event Log, the first time BESR was used it caused Events 11 and 12292 to occur These reference "The COM Server with CLSID {790f2886-9889-4c99-8ef5-531add05d044} and name SW_PROV" This is the COM+ component for the Symantec VSS provider Before this, there were no VSS errors in the history of the Application log After BESR was installed, when the scheduled backup by
VSS_WS_FAILED_AT_FREEZE - social. technet. microsoft. com Now though, when I attempt a VSS snapshot and that VM happens to be running, I get the VSS_WS_FAILED_AT_FREEZE error If that VM is not running, the VSS snapshot works fine
Hyper-V VM backups fail - ID 30290; Internal error code: 0x80990A00 Things I've tried: > Removed extra VSS providers from the Hyper-V host > Added [HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\UseSystemSoftwareProvider] to the registry on the Hyper-V host > Followed the steps for migrating from the system VSS provider to the hardware VSS provider > Verified that VDS VSS in the EqualLogic Group Manager has access to the cluster node
VSS provider is in a bad state error in DPM 2010 " The VSS application writer or the VSS provider is in a bad state Either it was already in a bad state or it entered a bad state during the current operation
VSS snapshot of VM in a SMB3 Share over a second nic we are currently implementing a backup solution to back up our HyperV2012R2 Failover Cluster VM's The VM's have their disks on a 2012 R2 StorageSpaces Server shared via SMB3 The 'file server vss agent' service is installed on the storage system