Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Backup Exec 2010 R2 - Final error: 0xe000fed1 - A failure occurred querying the Writer status

Created: 26 Dec 2012 • Updated: 26 Dec 2012 | 5 comments

All

We are running Backup Exec 2010 R2 Version 13.0 Rev. 4164 (32 bit) on 2003 R2 SP2

We are attempting to backup the system state of a Server 2008 R2 server but are having the following errors:

 

V-79-57344-65233 - AOFO: Initialization failure on: "\\SERVERNAME\System?State". 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: Automated System Recovery, Writer ID: {BE000CBE-11FE-4426-9C58-531AA6355FC4}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).
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).
Writer Name: Internet Information Services, Writer ID: {2A40FD15-DFCA-4AA8-A654-1F8C654603F6}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).
Writer Name: Internet Information Services, Writer ID: {59B1F0CF-90EF-465F-9609-6CA8B2938366}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).
Writer Name: Registry, Writer ID: {AFBAB4A2-367D-4D15-A586-71DBB18F8485}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).
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).

 I have checked and the BE VSS writer is not installed on the server we are trying to back up.

Any suggestions to resolve this issue would be greatly appreciated

Many thanks

Comments 5 CommentsJump to latest comment

RP765432's picture

Hi,

The VSS related events are as follows

If you need anymore information let me know

Thanks

Log Name:      Application
Source:        VSS
Date:          26/12/2012 12:26:08
Event ID:      13
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVERNAME
Description:
Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name Coordinator cannot be started. [0x80070005, Access is denied.
]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">13</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-12-26T12:26:08.000000000Z" />
    <EventRecordID>773863</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVERNAME</Computer>
    <Security />
  </System>
  <EventData>
    <Data>{e579ab5f-1cc4-44b4-bed9-de0991ff0623}</Data>
    <Data>Coordinator</Data>
    <Data>0x80070005, Access is denied.
</Data>
    <Data>
    </Data>
    <Binary>2D20436F64653A2041444D50524F434330303030313133392D2043616C6C3A2041444D50524F434330303030313132382D205049443A202030303030393831362D205449443A202030303030393933362D20434D443A202076737361646D696E20206C6973742070726F7669646572732D20557365723A204E616D653A204344462D5744552D5745422D30315C4E53554B2C205349443A532D312D352D32312D323531353836323739382D313833343535333930352D313334303430353733342D31303031202020</Binary>
  </EventData>
</Event>

 

Log Name:      Application
Source:        VSS
Date:          26/12/2012 07:03:03
Event ID:      8224
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      SERVERNAME

Description:
The VSS service is shutting down due to idle timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8224</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-12-26T07:03:03.000000000Z" />
    <EventRecordID>772290</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVERNAME</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>2D20436F64653A2020434F525356434330303030303737332D2043616C6C3A2020434F525356434330303030303735352D205049443A202030303030333035322D205449443A202030303030393339322D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>

 

 

 

 

Donald Eady's picture

Is this a newly created job or has this job run successfully in the past. 

 

From the cmd try running "vssadmin list writers" and look for writer failures

 

if you see any failures you may have to restart the server to stabalize the failing writer

 

View document below 

 

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

 

I hope this posting was helpful

  

CraigV's picture

...and also consider upgrading to BE 2010 R3 as this fixed a lot of issues experienced with previous versions of BE 2010.

You can download off the link below and use your current licenses. Grab copies of the Data/Catalogs folders before doing the upgrade if you so choose. Then run LiveUpdate to get SP2 and any subsequent patches, and then push-install these to any remote servers you might have!

http://trialware.norton.com/files/fc/Backup_Exec_2...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...