VSS Errors

What does the command: vssadmin list providers - show? Does it show them OK?

what is the output from

vssadmin list writers

Select allOpen in new window

My mistake, it instead of providers - should be writers...

It took about 15 minutes to finish but here is the output:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

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: {e872185e-bc69-4e4f-b677-ef06a5004c7a}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WIDWriter'
   Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
   Writer Instance Id: {cbb58c04-1a1c-4c2e-b05b-db16b9fd6c28}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {b2e911e8-bf03-4906-968d-2f9db66632e4}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {bd886497-0bf6-4447-9b92-c0e4ef2c856b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {723f626b-bc43-4e9c-a280-69fa32d4de16}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {2aac8fcd-7851-46d6-abff-db4a4d3f7e86}
   State: [1] Stable
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {95c15dfe-8114-44fe-9623-7d098f408eac}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {24359f84-e0d2-433d-b426-d4a169de1125}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {9137173a-61b2-4571-9c88-2421f07af9fd}
   State: [5] Waiting for completion
   Last error: No error


C:\Windows\system32>

Have you seen this article from MS: https://support.microsoft.com/en-us/kb/3098315
Says too many temp files in temp internet folder.

I was able to do that but that is where I then get confused what to do next. So I have the list of writers now what? Sorry I am noob when it comes to VSS writers.

You don't need to do anything with writers. They look ok in your case. What you need to do is to clean up the temp directories according to MS article.

run   vshadow command (vshadow C:) , Also clean snapshot and change to no limit the volumes on shadow copies properties and then restart the shadow copy service

Qill try tonight

Btw done of this stuff work I am still having the same issue.

Means? You have deleted the content of internet temp files?

Yea Still get the same error message and VSS takes forever to Queue.

Make sure you have followed the article again and then restart the Microsoft VSS service. Or reboot the machine ones the cleaning is done.
Additionally perform CHKDSK on all partitions with /f key.

No luck so far. I am still having the same issue. Sorry for the Delay

Can you post the most recent error? Is it still referring to the same source of the problem?

Yes same error.
2016-10-06_8-33-48.jpg

Just to save time for other users this I followed this
https://blogs.technet.microsoft.com/csstwplatform/2012/05/02/how-to-repair-vss-in-windows-2008/

Cool! Glad to hear you solved it!