I find many articles regarding this problem, and yet, following the instructions, several of my writers remain in "Waiting for Completion" status. I use Backup Exec and my backups have been failing for several days. I tried NT Backup and it also failed. Errors refer to corrupt objects and the specific errors point back to the Volume Shadow Copy service. I downloaded and installed KB940349 before I understood the problem, but it did not help. I tried the re-registering of the VSS components and that did not appear to change anything. Here is my VSSADMIN List Servers output:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {8feb8e19-8ec9-443e-9c7f-16d70de4a1fb}
State: [5] Waiting for completion
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {a45e8b9d-1da1-41e9-9035-4d67635e6e03}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {f6f6d028-ae89-497b-8c4a-1a5b620dbb99}
State: [5] Waiting for completion
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {f2b0f629-6ae6-4356-a853-3eb9e346a176}
State: [5] Waiting for completion
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {d7da3404-f808-499a-80ad-6d3d7f30c42d}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {488abb63-fb34-4408-af4c-18d12e655da4}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {3f283431-2835-4db3-810f-21766fb7060b}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {3f29b2e5-27ad-4f2a-ba27-40337c751163}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b8e359be-63c2-477c-820c-5764fb3b8c00}
State: [5] Waiting for completion
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {91ee8d9d-e281-49cb-badc-0094c33bb458}
State: [1] Stable
Last error: No error
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {69cad92b-5a18-4019-bba0-87697e2e16c4}
State: [5] Waiting for completion
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {34848545-3c28-45c8-9146-deff72fc206c}
State: [5] Waiting for completion
Last error: No error
I just read another tip that recommends a CHKDSK on the C: drive, followed by an SFC Scannow. I will do these but since I see no errors in the Event Log for the VSS service, I do not hold out much hope.