VSS writers inside virtual machine 'CONTOSO' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID 9851BE14-F276-459D-8D60-DF73B67EB658)

What does it mean? Writers on virtual machine are OK and all backups are successfull. Every day I have one 10172 event for one backup in Hyper-V-VMMS event log.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {17daa546-f2b5-44a8-b88f-31fae0650076}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {75f7fecf-4696-4f0e-8d09-19809d5f35da}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {204ef83b-d168-4179-a6aa-ef01e93dae7d}
   State: [1] Stable
   Last error: No error

Writer name: 'WIDWriter'
   Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
   Writer Instance Id: {b45a4a13-60a4-4f38-bdc0-c4cc748f3513}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {aca59bd3-2f19-4c76-b54a-28f2c2d95f73}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {41ef02d7-38b9-424a-b35b-a4b1cf79bd17}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {7a6ef84a-4fff-46ed-8921-da0d12fb5028}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {6d28a625-90a9-47a4-bf9f-fd8a6c76e770}
   State: [1] Stable
   Last error: No error

Writer name: 'MSMQ Writer (MSMQ)'
   Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Instance Id: {5bca99fe-6db6-4994-a744-e4149ba54364}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {d8249c2a-530f-48e9-92c3-179762ed0064}
   State: [1] Stable
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {51f5c94d-514b-4ca7-b5dd-2f11047d6a54}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {ce748865-451a-4189-8276-f2cb177629da}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {207fe098-42ab-430b-9285-c0b902729ade}
   State: [1] Stable
   Last error: No error

Hi, 

Please try to patch the virtual machines with hotfix for ntfs.sys to resolve the issue.

http://support.microsoft.com/kb/2866695

And then Updated integration services on the VM, for more detailed information, please refer to the article below:

PowerShell script to tell you if you need to update your Integration Services
http://blogs.msdn.com/b/virtual_pc_guy/archive/2013/04/29/powershell-script-to-tell-you-if-you-need-to-update-your-integration-services.aspx

Regards, 

Mandy

I am getting the same error in Hyper-v VMMs log on our 2012 R2 cluster nodes.

my VM has the up to date integration services and is 2012 server as well, so the Patch you have provided isn't applicable.

After this error the Hyper-v VSS Writer goes in to Failed state.

anyone else still having this issue ?

I am also getting the same errors in Hyper-V VMMs logs on Server 2012 R2.  VM is up to date with updates and Integration Services.

Anyone found a fix for this yet?

Thanks

I have the same error, but the backupjob is failed.

Hyper-V Windows Server 2012 R2 (all Patches up to date) and VM Guest Windows Server 2012 R2, Windows Server 2012 and Windows Server 2008 R2.

We are using DPM 2012 for Backup.

Any ideas?

Thanks.

After restarting the services "Hyper-V Virtual Machine Management" (vmms) the VSS Writer is in no error state.
VMs are still running while restarting the service but don't have management access.

The Backup is running at the moment. The root cause would be nice to know. 3 other servers are haveing the same problem.

Greets.

Did anyone find a fix for this? 

I have a cleanly installed two node Windows 2012 R2 Failover Cluster. Everytime I try to make a backup using Veeam I get this error: VSS writers inside virtual machine 'TESTVM' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID <long number>)

I have been troubleshooting with Veeam support for several days and we came to the conclusion that it has to do with VSS and that it is not Veeam related. This was confirmed using Microsoft VSS tools.

• Proposed as answer by Edmilson S. Filho Tuesday, May 27, 2014 8:03 PM

Hello, 

Install Service integration, apply latest atualuzaes in VMS and Hyper-V host to solve this problem.

Did anyone find a fix for this? 

I have a cleanly installed two node Windows 2012 R2 Failover Cluster. Everytime I try to make a backup using Veeam I get this error: VSS writers inside virtual machine 'TESTVM' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID <long number>)

I have been troubleshooting with Veeam support for several days and we came to the conclusion that it has to do with VSS and that it is not Veeam related. This was confirmed using Microsoft VSS tools.

Worked hard with Veeam support to find the source of the problem. It appeared that it was the configuration of the RAID, which caused a very poor write performance (10mb/s instead of 500mb/s). This was the cause of the time-out.

After enabling write caching on the RAID set, write speed went from 10MB/s to 500MB/s and the error and timeout no longer occurred.

So in my case it had nothing to do with Integration services or whatsoever. 

So for others experiencing this issue, also check the write performance of your SAN/DAS/NAS. If there are issues, try to figure out to improve this. For example, check the caching settings on the SAN/DAS/NAS.

• Edited by Erik Nettekoven Wednesday, May 28, 2014 11:12 AM
• Proposed as answer by Erik Nettekoven Wednesday, May 28, 2014 11:12 AM

I also get the Event ID 10172 while backin up virtual Machines (2008R2) on a HyperV 2012 R2 with Veeam BR 7 Patch 4.

Veeam error was:

14.06.2014 11:47:32 :: Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Crash consistent). Details: Guest processing skipped (check guest OS VSS state and integration components version)
 

Integration Components are the latest. A restart of the Guest VM doesnt help.

In my case the solution was to restart the service Hyper-V-Volumenschattenkopie-Anforderer in the Guest VM.

Regards

count

Please check during your backup schedule any other Hyper-V replication or Backup is running for particular Vm.

it happens when your VVS writer is busy with other backup.