Normally the System Writer will be in a failed or hung state like you have stated however with this specific error message all writers are in a no error state:
U:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
I have used a similar takedown to try to resolve the issue and while that has resolved other errors in the ast it doesnt seem to resolve this one.
We are using Netowrker Server 8.2.1.8 and Windows clients are all on 8.2.1 Build 681.
I have tried restarting services on the machine previously like you have stated and nothing seems to resolve this except for a reboot. It really feels like a windows patch started this as I have never seen these errors until about 6 months ago and some machines will start working and some continue to fail until they are rebooted.
bingo.1
2.4K Posts
0
January 11th, 2018 07:00
This is obviously due to problems with your 'VSS system'. Most likely not all writers are in a 'stable' state.
Check as follows:
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
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: {50ff9856-aaaa-4832-88df-6539728e1252}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {af8d8af7-176a-4ef8-83dd-6e6ba8b906eb}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {7b74ce90-1bfd-461d-87e2-e432ce7d1def}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {59b37491-26e1-44d3-abe1-4289a989652b}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {ed24e12c-9165-4abd-9148-ac1212ed74e5}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {2168e3b0-e6c4-442d-b859-26270b3f5f96}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {9d8c23be-89aa-44b3-bb6c-9159736456d6}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {aa5e06b1-2277-4af6-9e06-cf9877dfc23d}
State: [1] Stable
Last error: No error
C:\>
#####################
To correct that, you may either reboot the server or run this routine (as administrator):
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)
net stop cryptsvc
net start cryptsvc
net stop nsrpsd
net stop nsrexecd
net start nsrexecd
net start nsrpsd
If the issue still persists, restart the appropriate service.
And also use an appropriate NW client version (you did not state it).
sstevens916
2 Posts
0
January 11th, 2018 09:00
Bingo,
Normally the System Writer will be in a failed or hung state like you have stated however with this specific error message all writers are in a no error state:
U:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
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: {6d48f9b4-5209-4fbe-90f7-2254689b78de}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {57b40707-f807-4241-af36-c4e56dff4fc5}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {88cc290e-380e-480f-bb40-21db4199c76e}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {6918287b-4bf6-4fe7-bf34-6fcfc12da092}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {eb2383a6-90e7-49e8-a8ee-ef685f90a2e9}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e7c1f540-23e0-4f40-94a4-0161a1f50f38}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {beda0082-7383-415f-bb0f-ad26168d58a4}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {bf19bbba-3e21-4ec2-a0c2-653c5c6f18d8}
State: [1] Stable
Last error: No error
I have used a similar takedown to try to resolve the issue and while that has resolved other errors in the ast it doesnt seem to resolve this one.
We are using Netowrker Server 8.2.1.8 and Windows clients are all on 8.2.1 Build 681.
I have tried restarting services on the machine previously like you have stated and nothing seems to resolve this except for a reboot. It really feels like a windows patch started this as I have never seen these errors until about 6 months ago and some machines will start working and some continue to fail until they are rebooted.