Skip to main content

Hyper-V Server Backups Fail VSS

Thread needs solution

Hi, 

Trying to Backups Server2012 Core with Cluster Storage and getting the following Error:

---------------------------------------------------------------------------------------------------------------

Module 16

Message

Volume Tracker has failed to open session '5C36FD21-130E-02A4-137F-A361A2ADC1DE\Device\HarddiskVolume2' for volume 'C:'.

Additional info:

------------------------
Error code: 50294
Module: 16
LineInfo: 0xB1CECB03FB1D77AE
Fields: {"$module":"disk_bundle_vsa64_3622"}
Message: Volume Tracker has failed to open session '5C36FD21-130E-02A4-137F-A361A2ADC1DE\Device\HarddiskVolume2' for volume 'C:'.
------------------------
Error code: 4001
Module: 20
LineInfo: 0xD55ECF00C8D4289E
Fields: {"path":"volume_tracker_driver_api.dll","$module":"disk_bundle_vsa64_3622"}
Message:
------------------------
Error code: 65520
Module: 0
LineInfo: 0xBD28FDBD64EDB8F1
Fields: {"code":"2147942526","$module":"disk_bundle_vsa64_3622"}
Message: The specified module could not be found

---------------------------------------------------------------------------------------------------------------

VSSAdmin Shows this:

---------------------------------------------------------------------------------------------------------------

Writer name: 'Cluster Shared Volume VSS Writer'
   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
   Writer Instance Id: {df7f30c7-ead4-4296-b89c-bd4a4153e94d}
   State: [1] Stable
   Last error: Retryable error

---------------------------------------------------------------------------------------------------------------

Windows Log:

---------------------------------------------------------------------------------------------------------------

olume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process. 

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {445c1bff-cbe7-4fbf-921d-ae48934fe60d}

---------------------------------------------------------------------------------------------------------------

VM's On the cluster Backups no problem, Any Ideas?

Same error on both servers in in the failover cluseter.

Carl.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Carl,

From the Windows event log error:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Accès refusé.
. This is often caused by incorrect security settings in either the writer or requestor process.

You should check this event to see which user triggered the request. We've seen cases where snapshot creator user was NT Authority\System which was not added to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl (new DWORD-32 value). You should add the discovered user to this list and restart the VSS service. If the problem is still reproduced after these steps, please contact our support team for further assistance with the issue.

Thank you.

Vasily,

          I have the same issue, I am confused however as to where I am supposed to find the "user" that triggered the event? I have looked in the Acronis log from the back up and Windows Event Viewer. 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Chris,

The VssAccessControl user list must contain "NT Authority\System" user under it (+ "NT Authority\Network Service" - these are service users which are used to interact with VSS writers/providers. Note that depending on symptoms you might have a different issue than described in this thread (there are also cases where this VSS error is meaningless and doesn't affect anything), so in general it makes sense to continue troubleshooting with help from our support team and/or checking Windows Event logs for more errors related to VSS.

Thank you.