Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

e000fed1 - A failure occurred querying the Writer status.

Created: 03 Apr 2013 | 4 comments

Hi all,

I am having an error when trying to back up a terminal server (Server 2003) using Backup Exec 12.5.  The backup fails when backing up "Windows Management Instrumentation" in the Shadow Copy Components/Service State section of that remote agent.

e000fed1 - A failure occurred querying the Writer status.
For additional information regarding this error refer to link V-79-57344-65233

VSSAdmin doesn't seem to see anything amiss.  If I exclude WMI from the backups it works fine.  Any ideas on how to fix?

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

vssadmin list writers

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: {ea3b1b7b-805b-4534-ab9e-a1899f437e2b}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {1580907c-ecb3-4024-81d8-8cdb42e86b91}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {4b73cccb-6b70-474b-9fe8-abbf6a0051e3}
   State: [1] Stable
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {d2154980-6898-4b80-b162-3fae3ffe0281}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {e1f27344-d6c7-480e-ba7a-3249a9a7fa2a}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {fbb2c06c-61c8-4863-ad45-38e26855b5af}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {ec89506c-9c40-4c15-8ff6-5f57e3dc6f87}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {82661864-f984-4630-a399-5c756f1d6e88}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {ec7d6ee1-0786-4d55-be76-31bfb5cdabbc}
   State: [1] Stable
   Last error: No error
 

Operating Systems:

Comments 4 CommentsJump to latest comment

CraigV's picture

Hi,

There's a VSS Rollup Patch for Win2K3...even though your writers are stable now, it might be worth your while to install this patch. Once done, re-add the components left off from the System State and try running the backup again.

Thanks!

Alternative ways to access Backup Exec Technical Support:

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

Bizarro's picture

When doing step 1 of that guide (backing up WMI) I get prompted that the backup file already exists (no matter what unique filename I give it), if I click OK to overwrite I get a second error:  "Win32: The Specified module could not be found".

Maybe WMI is corrupted?