Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.

Created: 09 Oct 2012 • Updated: 25 Nov 2012 | 12 comments
This issue has been solved. See solution.

Running Backup Exec 12.0 Small Business Server Suite Rev. 1364 og getting random failing file data-backupjobs with error code E000FED1:

Backup- E: DataV-79-57344-34110 - 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).
Writer Name: Windows Internet Name Service, Writer ID: {F08C1483-8407-4A26-8C26-6C267A629741}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during thaw operation (10).
 
When running VSSADMIN LIST WRITERS - command from prompt I'm given the following output:
 
C:\Documents and Settings\xxx>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: {e1eae7cb-e621-4ab2-ba63-e5a534cc5e7a}
   State: [1] Stable
   Last error: No error
 
Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {51359454-ca5e-44f2-bbde-6fd81712dcc1}
   State: [1] Stable
   Last error: No error
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {dc2f12b7-d951-41ba-8724-bc474e7a5f7e}
   State: [1] Stable
   Last error: No error
 
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {5cb6d93a-bb72-4a0d-b90b-e6174402c580}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WINS Jet Writer'
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {a0bbbb7a-8d3d-47ae-93b2-7f7e008365d0}
   State: [10] Failed
   Last error: Retryable error
 
Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {3be2277a-66e1-43f1-a484-446320b9681f}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {23e6136d-6943-4108-90cb-a40089bad1b9}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {8ae68311-ead2-4af4-8009-874337783ecc}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {bc0eb6b5-835b-4a97-a8d0-7ba5f6db426e}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {8a3a101e-0dfd-46a2-9334-8ac0d57bf929}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {af7bf8db-a57e-47a8-a0b5-3a754d46f58a}
   State: [1] Stable
   Last error: No error
 
The following warnings and errors is shown in Windows Event Viewer:
 
Event Type: Error
Event Source: ESENT
Event Category: ShadowCopy 
Event ID: 2004
Date: 09-10-2012
Time: 01:09:09
User: N/A
Computer: SERVER01
Description:
wins (3316) Shadow copy 13 time-out (70000 ms).
 
Event Type: Warning
Event Source: VSS
Event Category: None
Event ID: 12290
Date: 09-10-2012
Time: 01:09:29
User: N/A
Computer: SERVER01
Description:
Volume Shadow Copy Service warning: ESENT ERROR {f08c1483-8407-4a26-8c26-6c267a629741} WINS Jet Writer: -2402.  hr = 0x00000000.
 
Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34113
Date: 09-10-2012
Time: 06:20:30
User: N/A
Computer: SERVER01
Description:
Backup Exec Alert: Job Failed
(Server: "SERVER01") (Job: "MANDAG-DATA") MANDAG-DATA -- The job failed with the following error: A failure occurred querying the Writer status.
 
The data selected for the backup-job is pure files and System State. 

The server is a Windows Small Business Server 2003 SP2.

Comments 12 CommentsJump to latest comment

CraigV's picture

Hi,

 

2 ways of troubleshooting this:

1. Restart the server giving you this error which will reset the VSS Writers.

2. Google and download the VSS Rollup Patch. Install this, restart the server and run the backup job again.

THanks!

Alternative ways to access Backup Exec Technical Support:

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

pkh's picture

You can use this document to trouble-shoot your VSS problem

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

You might also want to specifically choose the VSS provider.

 

SOLUTION
Donald Eady's picture

MJ TiT

 

What type of data is it that you are backing up?

I hope this posting was helpful

  

MJ TIT's picture

Alright, now a couple of days have gone. 

We've tried the following:

- Rebooted server. 

- Updated the VSS Update: KB940349

- Rebooted server again.

 

Now a new error is rechieved when running the backup-job:

 

V-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure". To make sure that the VSS is not disabled and can be started, click Control Panel, and then click Administrative Tools. Open the Services, and start Volume Shadow Copy. Check the Windows Event Viewer for details.
 
I've checked that the service is running and I've tried the following: http://www.symantec.com/docs/TECH66532
 
But I don't get the "Catastrophic failure"-error when opening DCOMCNFG utility.
 
Donald> The Data is normal files and system state.
 
 
pkh's picture

Have you tried explicitly selecting VSS as the provider like I have suggested above?

MJ TIT's picture

pkh> Yes, sorry. We've tried setting the Advanced Open File Option manually to "System - use Microsoft Software Shadow Copy Provider"

MJ TIT's picture

Error 8000FFFF as shown above:

 

V-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure". To make sure that the VSS is not disabled and can be started, click Control Panel, and then click Administrative Tools. Open the Services, and start Volume Shadow Copy. Check the Windows Event Viewer for details.
MJ TIT's picture

Actually, at the second try this might have helped. The backup was successful last night. I'm mark this as solution for now.

lmosla's picture

Hi,

Have you installed all the live updates on your Media Server?

In Windows services make sure the Microsoft Software Shadow Copy Provider and the Volume Shadow Copy services isnt started and that it is set to manual. 

Recreate your backup job into two new jobs with the flat files and the system state seperate.  In the system state portion run it wihout the Advanced Open File Option selected.

millertym's picture

I made sure no backups were activly running on our exchange server and then restarted the vss shadowcopy service and it solved backup issues that were reporting the errors mentioned in this article.  I also confirmed that exchange backups were not configured to use Advanced Open File Option.