cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Backup Exec 2012: VSS writer satus failed

ingamin
Not applicable

Hi Support,

1. I have Backup Exec 2012 and MS Exchange 2010 running on Windows 2008 R2 and when i do the backup i get this error:

Final error: 0xe000fed1 - A failure occurred querying the Writer status. See the job log for details about the error.

Final error category: Resource Errors

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

2. When i run the vssadmin list writers on both Exchange and Backup Exec servers i get:

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {1ff9fff4-6e3f-4446-b04b-cec88b556e22}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {df9e8302-1d9c-4ad1-a23d-24b5fbba89ff}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {7602d8db-5fa0-4b6e-b17e-ba6106d92f6b}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {48c611db-c1b4-4efc-8963-368e2d9efc04}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3a3932e1-9649-4474-a732-57873369314d}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {dd63630e-d9a0-4655-aecf-d157cddb02f9}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {0087b604-a385-4f40-86fe-a38c24788be4}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {ee66f785-caa5-465c-84fb-e192dd6d4304}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {0cf421a7-bd0b-4ae5-b01d-cc4e90bb691a}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {fe94b24c-d08e-452a-b887-9643396acf1c}
   State: [1] Stable
   Last error: No error

3. On Exchagne server the VSS is disabled on all drivers, except the drive C.

 

Please help,

Thanks Inga.

2 REPLIES 2

SuperBrain
Moderator
Moderator
Employee Accredited

Have you already attempted to troubleshoot this issue using the following technote?

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

If not i'd recommend you do that.. 
 

also see more solutions available on Symantec's knowledge base --> Click here

lmosla
Level 6

As stated in the above TechNote referenced by SuperBrain in 2008 systems a reboot will usually clear this error.