troubleshooting Question

VSS Writers in Failed State on SBS 2003 Server

Avatar of Nathan Kaufman
Nathan KaufmanFlag for United States of America asked on
Windows Server 2003SBSStorage Software
7 Comments3 Solutions2810 ViewsLast Modified:
I'm using StorageCraft Shadow Protect for a full system backup solution, after installing the software I keep getting VSS Writer fails, as listed below.  StorageCraft says it's not their problem and it's a Microsoft issue.  They say the writer switching modes is taking a while, sometimes over 2 minutes, and it usually should take only 15-20 seconds.  I tried re-registering DLL's, stoping or starting shadowcopy on the volume drive, and rebooting the server.  I still keep getting VSS in failed state.  I Was wondering what options out there that I have left to fix this issue.


C:\Documents and Settings\PCLINK>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: {388f968a-5eb5-44ce-974d-27d029888062}
   State: [9] Failed
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {d23bf6ca-8edd-4e7d-9793-72642350ca0e}
   State: [9] Failed
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {726a5a80-0d57-4457-86b0-a1efbd4e95d6}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {e24c8c31-dc8e-499d-bc34-fcf602e19156}
   State: [9] Failed
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {4cfa8afe-ca89-4e39-b56b-77004d24654b}
   State: [9] Failed
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {b1a56faa-2be0-4922-b11a-8fe9b2c7b930}
   State: [9] Failed
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {ede9cd40-6ddd-4d3a-aef7-581390606c40}
   State: [9] Failed
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {c70e13a5-9d05-4708-8c5b-a851d2a59fbf}
   State: [9] Failed
   Last error: No error

Writer name: 'WINS Jet Writer'
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {80d0a67d-9589-49d7-af42-bd427039a869}
   State: [9] Failed
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {6dba45cb-6851-49ab-9a67-592ca1fff2e8}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {2c1488ef-0cbd-4b1d-98f6-ba00ce48efa3}
   State: [9] Failed
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {0df26d93-3520-4742-b6c7-7a2e163eb396}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {1ebe8084-3727-4fc7-b4e0-fbb2a918146f}
   State: [1] Stable
   Last error: No error


C:\Documents and Settings\PCLINK>

Log from last three Backups:


          113C6A
11-Jul-2012 10:30:00 service 100 service (build 51) started job by incremental trigger
11-Jul-2012 10:30:00 service 104 4.2.5.16175 6264-96E2
11-Jul-2012 10:30:00 service 100 backup volume C:\ (NTFS)
11-Jul-2012 10:30:06 service 102 creating snapshot for  \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963}
11-Jul-2012 10:30:06 service 199 try snapshot by  VSS API by STC provider
11-Jul-2012 10:31:20 service 150 retrieving snapshot name.
11-Jul-2012 10:31:20 service 302 GetsnapshotName error VSS object not found
11-Jul-2012 10:31:22 service 199 try snapshot by  VSNAP API directly
11-Jul-2012 10:31:23 service 150 retrieving snapshot name.
11-Jul-2012 10:31:23 service 103 snapshot was created by  VSNAP API directly. It took 1 minutes and 17 seconds
11-Jul-2012 10:31:23 service 104 image will be created by VDIFF
11-Jul-2012 10:31:23 sptask 111 sbrun -mdn ( sbvol -fi \\?\STC_SnapShot_Volume_21_0 \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963} : sbcrypt -50 : sbfile -wd F:\StorageCraft\C_VOL-b006-i026.spi )
11-Jul-2012 10:31:23 sptask 110 Worker thread has started
11-Jul-2012 10:31:23 (loader) 112 corelogic version: 4.0.235.13839
11-Jul-2012 10:31:23 sbvol 109 free space exclusion on
11-Jul-2012 10:31:24 sbvol 107 incremental tracking is on, generation count: 26
11-Jul-2012 10:31:24 sbvol 117 incremental tracking is on, 638608 of 487990376 (0%) updated sectors
11-Jul-2012 10:31:26 sbvol 101 successfully opened volume \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963}
11-Jul-2012 10:31:26 sbvol 107 FAT system area sectors: 0
11-Jul-2012 10:31:26 sbvol 112 file \\?\STC_SnapShot_Volume_21_0\pagefile.sys excluded OK
11-Jul-2012 10:31:26 sbcrypt 109 filter started
11-Jul-2012 10:31:26 sbfile 101 successfully opened file F:\StorageCraft\C_VOL-b006-i026.spi
11-Jul-2012 10:31:26 sbvol 107 disk MBR sectors: 1
11-Jul-2012 10:31:26 sbvol 107 first track sectors: 63
11-Jul-2012 10:31:26 sbvol 109 disk CHS 30377/255/63 partition 1
11-Jul-2012 10:31:28 sbcrypt 107 compression mode: 5
11-Jul-2012 10:31:28 sbcrypt 107 encryption mode: 0
11-Jul-2012 10:31:49 sbvol 109 last volume read done
11-Jul-2012 10:31:49 sbcrypt 109 tail started
11-Jul-2012 10:31:49 sbcrypt 109 fini done
11-Jul-2012 10:31:49 sbfile 193 MD5:b425954c3e6e1c35338aedfae22ad86b F:\StorageCraft\C_VOL-b006-i026.spi
11-Jul-2012 10:31:49 sbfile 200 OK F:\StorageCraft\C_VOL-b006-i026.spi
11-Jul-2012 10:31:49 sbfile 109 fini done
11-Jul-2012 10:31:49 sbvol 109 incremental tracker reset OK
11-Jul-2012 10:31:49 sbvol 109 fini done
11-Jul-2012 10:31:49 sptask 114 Process finished successfully
11-Jul-2012 10:31:52 service 105 snapshots were destroyed


          115168
11-Jul-2012 12:00:00 service 100 service (build 51) started job by incremental trigger
11-Jul-2012 12:00:00 service 104 4.2.5.16175 6264-96E2
11-Jul-2012 12:00:00 service 100 backup volume C:\ (NTFS)
11-Jul-2012 12:00:05 service 102 creating snapshot for  \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963}
11-Jul-2012 12:00:05 service 199 try snapshot by  VSS API by STC provider
11-Jul-2012 12:03:03 service 150 retrieving snapshot name.
11-Jul-2012 12:03:03 service 302 GetsnapshotName error VSS object not found
11-Jul-2012 12:03:04 service 199 try snapshot by  VSNAP API directly
11-Jul-2012 12:03:20 service 302 Cannot take snapshot. Error: The semaphore timeout period has expired. 0x80070079(2147942521). Method:  VSNAP API directly. Volumes count: 1.
11-Jul-2012 12:03:20 service 301 Cannot take snapshot (The semaphore timeout period has expired. 0x80070079(2147942521)) - retry in 30 seconds
11-Jul-2012 12:03:50 service 199 try snapshot by  VSS API by STC provider
11-Jul-2012 12:05:34 service 150 retrieving snapshot name.
11-Jul-2012 12:05:34 service 103 snapshot was created by  VSS API by STC provider. It took 5 minutes and 29 seconds
11-Jul-2012 12:05:34 service 104 image will be created by VDIFF
11-Jul-2012 12:05:34 sptask 111 sbrun -mdn ( sbvol -fi \\?\STC_SnapShot_Volume_21_0 \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963} : sbcrypt -50 : sbfile -wd F:\StorageCraft\C_VOL-b006-i027.spi )
11-Jul-2012 12:05:34 sptask 110 Worker thread has started
11-Jul-2012 12:05:34 (loader) 112 corelogic version: 4.0.235.13839
11-Jul-2012 12:05:34 sbvol 109 free space exclusion on
11-Jul-2012 12:05:34 sbvol 107 incremental tracking is on, generation count: 27
11-Jul-2012 12:05:34 sbvol 117 incremental tracking is on, 744724 of 487990376 (0%) updated sectors
11-Jul-2012 12:05:55 sbvol 101 successfully opened volume \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963}
11-Jul-2012 12:05:55 sbvol 107 FAT system area sectors: 0
11-Jul-2012 12:05:56 sbvol 112 file \\?\STC_SnapShot_Volume_21_0\pagefile.sys excluded OK
11-Jul-2012 12:05:56 sbcrypt 109 filter started
11-Jul-2012 12:05:56 sbfile 101 successfully opened file F:\StorageCraft\C_VOL-b006-i027.spi
11-Jul-2012 12:05:56 sbvol 107 disk MBR sectors: 1
11-Jul-2012 12:05:56 sbvol 107 first track sectors: 63
11-Jul-2012 12:05:56 sbvol 109 disk CHS 30377/255/63 partition 1
11-Jul-2012 12:06:02 sbcrypt 107 compression mode: 5
11-Jul-2012 12:06:02 sbcrypt 107 encryption mode: 0
11-Jul-2012 12:06:30 sbvol 109 last volume read done
11-Jul-2012 12:06:30 sbcrypt 109 tail started
11-Jul-2012 12:06:30 sbcrypt 109 fini done
11-Jul-2012 12:06:30 sbfile 193 MD5:2fd9bb107d648d25d63b758c50ace25b F:\StorageCraft\C_VOL-b006-i027.spi
11-Jul-2012 12:06:30 sbfile 200 OK F:\StorageCraft\C_VOL-b006-i027.spi
11-Jul-2012 12:06:30 sbfile 109 fini done
11-Jul-2012 12:06:30 sbvol 109 incremental tracker reset OK
11-Jul-2012 12:06:30 sbvol 109 fini done
11-Jul-2012 12:06:30 sptask 114 Process finished successfully
11-Jul-2012 12:06:45 service 105 snapshots were destroyed


          116986
11-Jul-2012 13:30:00 service 100 service (build 51) started job by incremental trigger
11-Jul-2012 13:30:00 service 104 4.2.5.16175 6264-96E2
11-Jul-2012 13:30:00 service 100 backup volume C:\ (NTFS)
11-Jul-2012 13:30:05 service 102 creating snapshot for  \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963}
11-Jul-2012 13:30:05 service 199 try snapshot by  VSS API by STC provider
11-Jul-2012 13:31:21 service 150 retrieving snapshot name.
11-Jul-2012 13:31:21 service 302 GetsnapshotName error VSS object not found
11-Jul-2012 13:31:22 service 199 try snapshot by  VSNAP API directly
11-Jul-2012 13:31:23 service 150 retrieving snapshot name.
11-Jul-2012 13:31:23 service 103 snapshot was created by  VSNAP API directly. It took 1 minutes and 18 seconds
11-Jul-2012 13:31:23 service 104 image will be created by VDIFF
11-Jul-2012 13:31:23 sptask 111 sbrun -mdn ( sbvol -fi \\?\STC_SnapShot_Volume_21_0 \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963} : sbcrypt -50 : sbfile -wd F:\StorageCraft\C_VOL-b006-i028.spi )
11-Jul-2012 13:31:23 sptask 110 Worker thread has started
11-Jul-2012 13:31:24 (loader) 112 corelogic version: 4.0.235.13839
11-Jul-2012 13:31:24 sbvol 109 free space exclusion on
11-Jul-2012 13:31:24 sbvol 107 incremental tracking is on, generation count: 28
11-Jul-2012 13:31:24 sbvol 117 incremental tracking is on, 599679 of 487990376 (0%) updated sectors
11-Jul-2012 13:31:26 sbvol 101 successfully opened volume \\?\Volume{14d8e659-e990-11dc-818b-806e6f6e6963}
11-Jul-2012 13:31:26 sbvol 107 FAT system area sectors: 0
11-Jul-2012 13:31:26 sbvol 112 file \\?\STC_SnapShot_Volume_21_0\pagefile.sys excluded OK
11-Jul-2012 13:31:26 sbcrypt 109 filter started
11-Jul-2012 13:31:26 sbfile 101 successfully opened file F:\StorageCraft\C_VOL-b006-i028.spi
11-Jul-2012 13:31:26 sbvol 107 disk MBR sectors: 1
11-Jul-2012 13:31:26 sbvol 107 first track sectors: 63
11-Jul-2012 13:31:26 sbvol 109 disk CHS 30377/255/63 partition 1
11-Jul-2012 13:31:27 sbcrypt 107 compression mode: 5
11-Jul-2012 13:31:27 sbcrypt 107 encryption mode: 0
11-Jul-2012 13:31:52 sbvol 109 last volume read done
11-Jul-2012 13:31:52 sbcrypt 109 tail started
11-Jul-2012 13:31:52 sbcrypt 109 fini done
11-Jul-2012 13:31:52 sbfile 193 MD5:48fd1087047832a89780e8889531bfda F:\StorageCraft\C_VOL-b006-i028.spi
11-Jul-2012 13:31:52 sbfile 200 OK F:\StorageCraft\C_VOL-b006-i028.spi
11-Jul-2012 13:31:52 sbfile 109 fini done
11-Jul-2012 13:31:52 sbvol 109 incremental tracker reset OK
11-Jul-2012 13:31:52 sbvol 109 fini done
11-Jul-2012 13:31:52 sptask 114 Process finished successfully
11-Jul-2012 13:31:55 service 105 snapshots were destroyed
ASKER CERTIFIED SOLUTION
Member_2_4984608

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 3 Answers and 7 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 3 Answers and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros