cancel
Showing results for 
Search instead for 
Did you mean: 

A failure occurred querying the Writer status Backup exec 2010

babalojaan
Level 4

Hi,

My seupt
**********

- Windows 2003R2 standard
- Backup Exec 2010

My Problem
*************
The job failed with the following error: A failure occurred querying the Writer status.

Job Completion Status
		Job ended: den 21 april 2010 at 20:30:41
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-65233

 

 

		
		Backup- SERVER011
Writer Name: Dynamic Host Configuration Protocol, Writer ID: {BE9AC81E-3619-421F-920F-4C6FEA9E93AD},...V-79-57344-65233 - AOFO: Initialization failure on: "\\SERVER01\Shadow?Copy?Components". Advanced Op...
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Dynamic Host Configuration Protocol, Writer ID: {BE9AC81E-3619-421F-920F-4C6FEA9E93AD},...
V-79-57344-65233 - AOFO: Initialization failure on: "\\SERVER01\System?State". Advanced Open File Op...
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Dynamic Host Configuration Protocol, Writer ID: {BE9AC81E-3619-421F-920F-4C6FEA9E93AD},...


- I have restarted all the servers
- The job worked a few times, but it fels now
- please help!
7 REPLIES 7

RahulG
Level 6
Employee
Install the VSS rollup patch http://support.microsoft.com/kb/940349 (Reboot required) on the problem server and perform backups

babalojaan
Level 4
Thanks Raul for reply

i forgot to mention that the servers that i CAN NOT backup is windows 2008R2 and the link you gave me is for windows 2003.

 

RahulG
Level 6
Employee
1. Open Windows services and stop the Remote Agent for Windows Systems
2. Open Windows Explorer and go to X:\Program Files\Symantec\Backup Exec\RAWS
3. Rename the "bedsshadow.dll" file (see Figure 2.)
4. Restart the Remote Agent for Windows Systems  
5. Perform a backup of the remote system

Rreapply or update to the latest Windows Service Pack or contact Microsoft to further investigate the issue.

RahulG
Level 6
Employee
Aslo set the startup type for the Volume Shadow Copy Service to Manual.

Abhishek_Pradha
Level 2

For Gods sake, please remove the Tag for the "Connect and Protect Contest". These posts are stepping into the Security forums and my mailbox s literally getting flooded with these notifications for BackupExec.

@Mods / Eric: Can someone please remove the Connect and Protect Category from all other boards except the SEP Board?

Mikka
Level 3

The above rename of the DLL causes a "Communications Failure"

"Job ended: Tuesday, September 21, 2010 at 11:56:16 AM
Completed status: Failed
Final error: 0xe000fe30 - A communications failure has occurred.
Final error category: Server Errors

For additional information regarding this error refer to link V-79-57344-65072"
 

 

Mikka
Level 3

I reversed all of the changes, renaming the 'BEDSSHADOW.DLL' back to its original name, and restarting the 'Backup Exec Remote Agent for Windows Systems'

I re-ran my Exchange Differential and it completed successfully.

... gremlins! I'm just going to chalk it up to gremlins.