troubleshooting Question

VSS Writers Timed out

Avatar of Linear-IT
Linear-ITFlag for United States of America asked on
Windows Server 2008
4 Comments1 Solution6101 ViewsLast Modified:
hey everyone.  I am having an issue with Server 2008R2 Enterprise VSS.
I am using ArcServ backup to baackup all my servers.  This one particular server, which has MSSQL 2008R2 standard installed is the one giving me the issue.  The backup fails due to unable to work with VSS, when looking into the event logs for that server i am getting: EventID 12292
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({8389f6ec-6d69-4d23-8a2d-8449a5498d81}) [hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
].
Operation:
   Executing Asynchronous Operation
Context:
   Current State: DoSnapshotSet


Event ID 8193
Volume Shadow Copy Service error: Unexpected error calling routine Cannot find anymore diff area candidates for volume \\?\Volume{208952c7-c016-11df-bebe-806e6f6e6963}\ [0].  hr = 0x8000ffff, Catastrophic failure
.
Operation:
   Automatically choosing a diff-area volume
   Processing EndPrepareSnapshots
Context:
   Volume Name: \\?\Volume{208952c7-c016-11df-bebe-806e6f6e6963}\
   Execution Context: System Provider

When i run the vassadmin list writers command i get the following readout
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 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: {b6f552a2-b25f-4a7c-95df-dece521388a5}
   State: [7] Failed
   Last error: Timed out

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {97e592f9-d6c4-4360-9da9-24dc36855fce}
   State: [7] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {fb333aa0-8836-488c-a43c-13838589f32b}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {4d7b79e0-97ec-42e6-bd12-0d17a000a9ec}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {887d5ab8-5a89-4f20-9fb4-db493f12d0e3}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {43288689-f5c9-4aad-b8ee-65d59e1a5e1b}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {b223cb20-47fe-4d4f-b942-a8ef8f6d4b33}
   State: [7] Failed
   Last error: Timed out

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {5a1d7fe6-ba86-4dc2-bff0-48a383d6c16b}
   State: [7] Failed
   Last error: Timed out

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {ebc64ef6-265e-407e-adaa-717fee3e5522}
   State: [7] Failed
   Last error: Timed out

As you can see, a few of the writers are timing out.  I, just in case something was acting all wonky i re-registered all the DLL's needed for teh service as well as rebooted the server.  When the server came back up all the writers were working without issue, when i ran the backup again, they timed out.  Has anyone ever run into this before?  I am leaning toward the ArcServ backup agent might be causing issues but cannot figure out where.
Thoughts?
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros