Forum Discussion

Phorward's avatar
Phorward
Level 3
15 years ago
Solved

VSS Snapsot Error on Win 2008 R2 DC with BE 2010 (Error V-79-10000-11217)

 

I've searched the forums but didn't find anything that looked like it could solve my problem.

 

I'm getting errors backing up a Windows Server 2008 R2 Domain Controller.

The machine is a HP Proliant DL380 G5, a new installation running DC, DNS, DHCP and a Fax application with a modem on the serial port.

This is the error message in the backup log:

 - AOFO: Initialization failure on: "\\SERVER03\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11217 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.
 - AOFO: Initialization failure on: "\\SERVER03\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11217 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.

 

I get these errors when running vssadmin list writers:

 

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {3f93c30a-1a4d-4cd9-8c7d-3d31c5d1a8f9}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {324f56fe-2a72-4ac9-92e1-6ae8c58447dc}
   State: [7] Failed
   Last error: Timed out

Writer name: 'WINS Jet Writer'
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {d4b83889-75fc-4746-ba66-01b100002a00}
   State: [7] Failed
   Last error: Timed out

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {db4a8e85-8c2b-4bef-a6d3-c30352ccbccb}
   State: [7] Failed
   Last error: Timed out

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {b0ac3a61-027b-4b79-9741-84af1f2d79d9}
   State: [7] Failed
   Last error: Timed out

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {59bb6c43-158d-4283-aa5b-068954cb9b9b}
   State: [7] Failed
   Last error: Timed out

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {f3604e28-91c0-4bb7-852d-4a85aa3b2874}
   State: [7] Failed
   Last error: Timed out

 

A reboot of the server didn't help.

The backup server is running Backup Exece 2010 v13.0 Rev. 2896 (32-bit) on Windows Server 2003.

  • Why should I mark it as solved when it isn't solved?

    I have now investigated further and it turned out to be a USB to Serial Port device that caused the trouble. After the device was removed the Volume Shadow Copy started working.

    Now the cased is solved.

  • Hi ,

     

    Please try this

     

    http://www.symantec.com/docs/TECH138359

     

    Also if this doesnot help may be do restart & check & still if the writer shows failed state

     

    You will have to open a case with Microsoft were they can debug VSS to understand were is the issue & fix it in that case it will ne out of scope of this forum

     

    Please mark this solved if this help you

     

    Thank You

  • Thanks for the advice.

    I will contact Microsoft and see if they can assist.

  • Hi

     

    Thanks for your response on same

     

    Can you please mark the post solved so that we can close the thread

     

    Thank You

  • Why should I mark it as solved when it isn't solved?

    I have now investigated further and it turned out to be a USB to Serial Port device that caused the trouble. After the device was removed the Volume Shadow Copy started working.

    Now the cased is solved.