Link to home
Start Free TrialLog in
Avatar of Mike Lazarus
Mike LazarusFlag for Australia

asked on

The SharePoint 2010 VSS Writer service keeps becomming disabled...

SBS2011 ... fully patched
The Sharepont VSS writer (SPWriterV4) keeps becoming "Disabled" ... not just stopping.

I detect it and run this as an admin:
sc config SPWriterV4 start=  delayed-auto
net start SPWriterV4

Open in new window

But in a minute, I'll have a series of Event Logs like:

Log Name:      Application
Source:        VSS
Date:          22/12/2012 16:52:05
Event ID:      8230
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      MONTY-SBS2011.glcomputing.local
Volume Shadow Copy Service error: Failed resolving account spfarm with status 1376. Check connection to domain controller and VssAccessControl registry key. 

   Initializing Writer

   Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Name: Registry Writer

Error-specific details:
   Error: NetLocalGroupGetMemebers(spfarm), 0x80070560, The specified local group does not exist.

Open in new window

I get a about 10 of those (different "Writer Name") ... then it stops and becomes Disabled.

I've tried this MS suggestion:

And re-doing the passwords like the first suggestion here:

Any other suggestions?
Avatar of David Atkin
David Atkin
Flag of United Kingdom of Great Britain and Northern Ireland image

Have you install a sharepoint update recently? If so did you run psconfig?
Also after the MS fix did you restart the CSS service?
Avatar of Mike Lazarus


psconfig long since run

Yes, I run a bat with the two lines from at the top of the post ... the first to set it from "disabled", the 2nd to start it
And of course... the real issue is ... backups don't run
Been through all ... none of them address the VSS Writer becoming disabled :-(
To be clear, I did:
Sharepoint 2010 Products Configuration - but didn't create a new site
Removed the accounts from VssAccessControl - was done before as per MS link in original post.

If I accept that those log entries can be ignored (from another MS article) ... I still can get past the service becoming DISABLED (not just stopped). This means I also can't backup

The VSS Writer
Avatar of Mike Lazarus
Mike Lazarus
Flag of Australia image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Did you solve it? We're having exact the same problem here :-/
I found this link that may help!

It's long winded but I think this might be it


I've had the same issue also
Never got this fully resolved ..