Creating protection for Hyper-V VMs on Windows Server 2012 fails with Internal error code 0x809909E2


When using System Center 2012 Data Protection Manager (DPM) SP1 to create a protection group for a Hyper-V workload that is running on Windows Server 2012, the protection will not complete. The symptoms vary based on the configuration of the Hyper-V server.

For stand-alone Hyper-V server

In DPM, creation of the protection group will fail with the error:

Type: Replica creation
Status: Failed
Description: Failure occurred while adding one or more of the volumes involved in backup operation to snapshot set. Please check the event log on %HypervServer%.lab to troubleshoot the issue. (ID 30290 Details: Internal error code: 0x809909E2)
 More information
End time: 
Start time: 
Time elapsed: 00:00:05
Data transferred: 0 MB
Cluster node -
Source details: \Backup Using Child Partition Snapshot\Server1
Protection group: Protection Group 1

For both stand-alone and CSV Hyper-V

On the Hyper-V server, the application event log will show Event IDs 12292 and 13 from VSS:

Log Name:      Application
Source:        VSS
Event ID:      12292
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {463948d2-035d-4d1d-9bfc-473fece07dab} [0x80070005, Access is denied.].

Log Name:      Application
Source:        VSS
Event ID:      13
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Volume Shadow Copy Service information: The COM Server with CLSID {463948d2-035d-4d1d-9bfc-473fece07dab} and name HWPRV cannot be started. [0x80070005, Access is denied.]


This is caused by the iSCSI Target Storage Provider returning an unexpected state.


There are two options to workaround this issue.

Option One:

Create a registry key to force DPM to skip trying any hardware providers:

HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\UseSystemSoftwareProvider

  • Presence of this key will force DPM to use the software provider, so if you have and want to use a hardware provider do not use this key. Likewise, if you add a hardware provider in the future you will need to remove it.
  • This is a key under Agent and not a value.
  • This must be added to each node of the CSV cluster that DPM is using (has an agent on).
  • This does not require a reboot of the nodes.
Option Two:

One the Hyper-V server(s) involved, remove the iSCSI Target Storage Provider (VSD and VSS) by using the Add Roles and Features Wizard.  It is a Role under the File And Storage Services/File and iSCSI Services area.

More Information

The Hyper-V servers will also have the following logged in the Program Files\Microsoft Data Protection Manager\DPM\Temp


146C 1140 09/25 04:00:54.578 31 vsssessioncontext.cpp(143) [0000000001D8EEC0]  WARNING </VSS_CONTEXT>
146C 1384 09/25 04:01:24.581 31 vsssnapshotrequestor.cpp(645) [0000000001D86690]  WARNING Failed: Hr: = [0x80042316] : CSV2 Snapshot failed with UnexpectedProviderError (0x8004230F), Mapping it to SnapshotSetInProgress error, Volume: \\?\Volume{e1b5c403-3d99-4c5c-a521-840f1b61bb75}\
146C 1384 09/25 04:01:24.581 31 createsnapshotsubtask.cpp(1780) [0000000001D87FB0]  WARNING Failed: Hr: = [0x80042316] : Encountered Failure: : lVal : pSnapshotRequestor->StartPrepareForBackup(snapshotSetId, m_fUseSystemSoftwareProviderOnly)
146C 1384 09/25 04:01:24.581 05 fsmstate.cpp(167) [0000000001D8CE70]  WARNING Failed: Hr: = [0x80042316] : Encountered Failure: : lVal : pTransition->Execute(pEvent)
146C 1384 09/25 04:01:24.581 05 genericfsm.cpp(225) [0000000001D8D3F0]  WARNING Failed: Hr: = [0x80042316] : Encountered Failure: : lVal : m_pCurrentState->SendEvent(pEvent, pNextState)
146C 1438 09/25 04:01:24.581 31 hypervwriterhelperplugin.cpp(535) [0000000001D8C1D0]  NORMAL Component 80DC3791-5605-4EC3-AE14-1D742C8A6AF5 is a VM
146C 1438 09/25 04:01:24.607 31 vsssnapshotrequestor.cpp(544) [0000000001D86690]  NORMAL CVssSnapshotRequestor::StartPrepareForBackup [0000000001D86690]
146C 1438 09/25 04:01:24.612 31 vsssnapshotrequestor.cpp(593) [0000000001D86690]  NORMAL CVssSnapshotRequestor: Using provider {00000000-0000-0000-0000-000000000000} for volume \\?\Volume{e1b5c403-3d99-4c5c-a521-840f1b61bb75}\
146C 1438 09/25 04:01:24.643 31 vsssessioncontext.cpp(143) [0000000001D8EEC0]  WARNING <VSS_CONTEXT><COMPONENTS><COMPONENT><WriterId>{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}</WriterId><WriterName></WriterName><LogicalPath></LogicalPath><ComponentName>80DC3791-5605-4EC3-AE14-1D742C8A6AF5</ComponentName><ComponentType>2</ComponentType></COMPONENT></COMPONENTS><SNAPSHOT_CONTEXT>          SelectComponent = 1,          PartialFileSupport = 0,          BootableState = 0,          BackupType = 1,          SnapshotContext = 0,          SnapshotAttributes = VSS_CTX_BACKUP          </SNAPSHOT_CONTEXT><SnapShotVolumes><Volume>              <Name>\\?\Volume{e1b5c403-3d99-4c5c-a521-840f1b61bb75}\</Name>              <SnapshotPath>(null)</SnapshotPath>              <MountPoint>C:\ClusterStorage\volume2\</MountPoint>              <MountPointArray></MountPointArray>              <SnapshotId>{00000000-0000-0000-0000-000000000000}</SnapshotId>              <ProviderId>{00000000-0000-0000-0000-000000000000}</ProviderId>              <IsHardwareProvider>0</IsHardwareProvider>              </Volume></SnapShotVolumes>