cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

A failure occurred querying the Writer status.

I am running a windows 2003 (SP1) server running BE 9.1, I am receiving the writer status error almost everyday. I have ran the vssadmin list writers and all are fine with no errors; and have rebooted the server almost daily. Sometimes it works after and other times it does not. More so on the not side.
I have also tried to registering the 32 bit Object Linking and Embendding DLL with no luck.
If I perform a backup with the embedded windows backup it works fine. it is only with BE that i get the writer status error. Even right after the backup fails i runt he vssadmin and all the writers are fine. Any suggestions would be GREATLY appreciated.
8 Replies
Highlighted

Re: A failure occurred querying the Writer status.

Sorry I can't help but I am getting the same error: 0xa00fed1 A failure occurred querying the Writer status.

I am running windows 2003 SP1 BE 9.1 Rev 4691. This is my first time getting this error.

Suggestions welcome here too.
Highlighted

Re: A failure occurred querying the Writer status.

Same error here.

It was working fine until last Friday Jan 26 2007. I have Win2003 Std Edition, SP1 and BE 10.0 Rev 5520 SP1, Hot fixes 13 and 15. I am NOT running MS Exchange in this server. The System Event Logs don't show any backup related errors.

The error is this:

AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.

Check the Windows Event Viewer for details.
Writer Name: Event Logs, Writer ID: {EEE8C692-67ED-4250-8D86-390603070D00}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Consult your Microsoft documentation for details. Check the Windows Event Viewer for corresponding application or system errors.
Writer Name: Removable Storage Manager, Writer ID: {5D3C3E01-0297-445B-AA81-A48D7151E235}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Consult your Microsoft documentation for details. Check the Windows Event Viewer for corresponding application or system errors.
Writer Name: Windows Management Instrumentation, Writer ID: {A6AD56C2-B509-4E6C-BB19-49D8F43532F0}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Consult your Microsoft documentation for details. Check the Windows Event Viewer for corresponding application or system errors.
Writer Name: COM+ Class Registration Database, Writer ID: {542DA469-D3E1-473C-9F4F-7847F01FC64F}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Consult your Microsoft documentation for details. Check the Windows Event Viewer for corresponding application or system errors.
Writer Name: Registry, Writer ID: {AFBAB4A2-367D-4D15-A586-71DBB18F8485}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Consult your Microsoft documentation for details. Check the Windows Event Viewer for corresponding application or system errors.
Writer Name: System Files, Writer ID: {E8132975-6F93-4464-A53E-1050253AE220}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Consult your Microsoft documentation for details. Check the Windows Event Viewer for corresponding application or system errors.
==========

And the output of VSSADMIN LIST WRITERS is this:

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

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {e9daf20b-27dc-497e-a8aa-ca01cc5a0290}
State: Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {d84a0344-595b-4bed-bc1e-4b56edc8e7dc}
State: Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {5907736e-f89e-42c1-93ce-56b040e82979}
State: Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {a8a277a5-0444-463a-a174-9f2d06b94514}
State: Stable
Last error: No error

Writer name: 'Removable Storage Manager'
Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
Writer Instance Id: {e066e00c-dde3-4a54-9b9e-2173605f329f}
State: Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {8ea87382-c545-4618-adc6-8886e7e00b9f}
State: Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {a8aeb84b-627c-4414-b7e5-b6ba0e4debe7}
State: Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {4b491e98-4a6b-4a36-94cb-030f82a22e9f}
State: Stable
Last error: No error
===============

I would appreciate any help on this issue.
Highlighted

Re: A failure occurred querying the Writer status.

Hello Michael,


The following document should help you resolve the issue.



http://support.veritas.com/docs/261993

Thank You,

Shweta
Highlighted

Re: A failure occurred querying the Writer status.

Hello Shweta,

It might work for Michael but not for me (please read my posting above in the thread).

Any advise for me?

Thank you.
Highlighted

Re: A failure occurred querying the Writer status.

I have downloaded the fix from http://support.microsoft.com/kb/903234/en-us and i am installing it now. Once the backup runs this evening i will let every know if it helped.
Highlighted

Re: A failure occurred querying the Writer status.

I tried the update and still getting the error. Have rebooted and checked the all the writer stats and all show no errors, but still no luck
Highlighted

Re: A failure occurred querying the Writer status.

I'm getting the same in a restore job, which is even worse in my opinion.

Everything is patched to the hilt, and I have dedicated servers so I can rule out any compatibility issues. Thankfully it's only a test restore, but I can only say that my confidence is somewhat dented, and I'm hoping that I never have to do it for real... Smiley Sad
Highlighted

Re: A failure occurred querying the Writer status.

I was able to finally run a succesful backup of my system state by referencing the following MS KB article.