Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows Server 2003 backup error: a000fed1 HEX

Status
Not open for further replies.

sonicman

MIS
May 10, 2001
10
US
When backing up a few (not all) of the Windows Server 2003 machines in our domain, we see this error reported in the event log:

Final error code: a000fed1 HEX

Final error description: A failure occurred querying the Writer status.

Has anyone else seen this error before, and if so, do you know the cause/solution?

Thanks,

Jeremy Ochoa
Lockheed Martin Information Technology
Jeremy_S_Ochoa@rl.gov
 
sonicman

from a dos prompt on the windows 2003 server run this command

vssadmin list writers

from the list - make sure they are all in a stable state - if not try rebooting the server - is this doesn't fix it - you will need to see MS about getting these fixed.

Also, make sure you are using 9.0 revision 4454, as this is the only version which supports windows 2003.
 
I'm am most recently having the same problem.

My results of vssadmin list shows the DHCP writer has failed - retryable error.

Restarting the server has had no positive results.

Any other thoughts?
 
Im receiving the same error, its occurring while trying to backup the shadow copy

Error code : a000fed1 HEXError description : A failure occurred querying the Writer status.

My results of vssadmin are as follows:

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {bbbcee61-5443-4f3b-bfd7-ee8107738061}
State: [9] Failed
Last error: Retryable error

Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {9fc99e4a-2914-4875-b828-4a370193e5c8}
State: [9] Failed
Last error: Retryable error

With 7 more writers that have no errors
I will try a reboot at the end of the day!

-c0s
 
After inspection I notices some of the RANT32 builds on remote workstations / servers wasn't the most current.

I've uninstalled the existing and installed the most current RANT version builds and am running a full backup test now.

I'll advise as to the results.
 
After reinstall of all RANT agents (manually removed) and reinstalled - backup job completes without issue.

Hope this is usefull
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top