A failure occurred querying the Writer status

Hi All

We have a client running on SBS 2008 with BackupExec 2010 R2.Recently we are getting the following error message

The job failed with the following error: A failure occurred querying the Writer status

Following is listed In the backup exec job log

Job ended: 26 October 2011 at 04:09:12
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors

Backup
V-79-57344-65233 - 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: Dynamic Host Configuration Protocol, Writer ID: {BE9AC81E-3619-421F-920F-4C6FEA9E93AD}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).

Writer Name: File Server Resource Manager, Writer ID: {12CE4370-5BB7-4C58-A76A-E5D5097E3674}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).

Writer Name: Network Policy Server, Writer ID: {35E81631-13E1-48DB-97FC-D5BC721BB18A}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).

Writer Name: Terminal Services Gateway, Writer ID: {368753EC-572E-4FC7-B4B9-CCD9BDC624CB}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).

Writer Name: Windows Management Instrumentation, Writer ID: {A6AD56C2-B509-4E6C-BB19-49D8F43532F0}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).

Also when I list the VSS Writers following is the outcome

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {9f23e470-6f2a-49f6-b4d6-ba013470e95e}
State: [1] Stable
Last error: Non-retryable error

Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {11c433d7-7683-4513-b7e0-c42dfca11f41}
State: [5] Waiting for completion
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {15a6a721-77aa-491b-97a4-a38f3193da00}
State: [5] Waiting for completion
Last error: No error

Writer name: 'SharePoint Services Writer'
Writer Id: {c2f52614-5e53-4858-a589-38eeb25c6184}
Writer Instance Id: {ce2dda01-9d24-46fd-bffa-4201eb5847a1}
State: [1] Stable
Last error: Non-retryable error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {782f76e8-5977-4877-9ac1-d653d65e222e}
State: [5] Waiting for completion
Last error: No error

Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id: {19a5c8af-ac1c-49b4-b948-e93d60977ae5}
State: [5] Waiting for completion
Last error: No error

Writer name: 'SPSearch VSS Writer'
Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
Writer Instance Id: {8c83396b-026e-4941-a126-5f9e2454ee07}
State: [1] Stable
Last error: Non-retryable error

Writer name: 'TS Gateway Writer'
Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
Writer Instance Id: {48a39207-0dce-497f-855a-076c912f42db}
State: [9] Failed
Last error: Timed out

Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {d7057fd0-77e0-4f7c-831f-7788b779bf04}
State: [5] Waiting for completion
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {a4900116-94e2-4268-ac95-eac9732b1a23}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {f96871cd-425c-4c75-b1d6-7239d8827f39}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {e63de783-ae27-41e5-9bdd-6725442f69a8}
State: [5] Waiting for completion
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {6e8655a5-9255-4726-af18-6a8400f492be}
State: [5] Waiting for completion
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {30ce706d-f924-4cb4-9175-c146da14e593}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {2646bfad-cc9a-44e7-98f0-7dcdb6c805df}
State: [5] Waiting for completion
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0de29bcd-7c3b-46b9-a01a-d70f677ff0b4}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {3bb4516a-86df-4ed2-9bdd-b67c700fabd8}
State: [11] Failed
Last error: Retryable error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {f686da00-1b1c-47d9-b760-3fcee3756ce9}
State: [5] Waiting for completion
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {80683169-24d1-49a5-9824-75a933d111d0}
State: [5] Waiting for completion
Last error: No error

Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {a32e1059-cdd0-4a11-be20-70fb7967d48d}
State: [9] Failed
Last error: Timed out

 

Additionally can see the following error messages on the application event log for all the mentioned writers in the backup exec job log

Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum supported limit. hr = 0x80042409.

Operation:
PostSnapshot Event

Context:
Maximum supported sessions: 64
Completed sessions: 8
Active sessions: 64
Aborted sessions: 0
Writer failed sessions: 0
New snaphot set: {9bb8dc03-6a08-45b5-84e5-d5536437a5f3}
Old snapshot set: {586def6f-faf5-4718-ad12-623edc7fcacc}
Old operation: 1013
Old state: 5
Old failure: 0
Execution Context: Writer
Writer Class Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Name: FRS Writer
Writer Instance ID: {15a6a721-77aa-491b-97a4-a38f3193da00}

This issue will not occur only fo a copule of days  if the server is rebooted

Would greatly appericiate if someone can let us know a permanent solution

Many thanks,

Dhanushka