Answered by:
How do i resolve Event ID: 8230 Source VSS with SBS 2011?

-
We're having a problem with one of the volumes not backing up. It apears to be linked to the VSS writer.
Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.
Operation:
Gathering Writer Data
Executing Asynchronous Operation
Context:
Execution Context: Requestor
Current State: GatherWriterMetadata
Error-specific details:
Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.
It appears to be telling me that the groups dont exist when they do. I've trawled through quote a few google results on this but so far have not found a way of resolving the issue.
Any help would be much appreciated.
Thanks
Question
Answers
-
I was receiving the same error on a clean install of SBS 2011 Standard with all service packs and updates from Microsoft Update.
I found the following link which mentions accounts that are enabled to create VSS copies: http://www.eventid.net/display.asp?eventid=8230&eventno=10589&source=VSS&phase=1
Using the information from there as a starting point, I did the following:
- open registry editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
- backup this key, just in case you need to restore it later
- CHANGE the value to 0 for all accounts except the NetworkService account which I left at 1
- close registry editor
- open services.msc and restart Volume Shadow Service
- retry Windows Server Backup
This time the backup was able to successfully create the volume shadow copies and continue. I am not sure yet what the consequences are for disabling these other accounts from creating VSS copies, but a successful backup is more important at the moment!
Andrew McMenimen
Concierge Computer Support - www.conciergecomputer.net
- Proposed as answer by Rick TanModerator Monday, July 11, 2011 3:37 AM
- Marked as answer by mpjubb Monday, July 11, 2011 6:03 AM
-
Hi:
Here is a link to the list of SBS 2011 errors that can be ignored on SBS 2011. However, if you have further evidence that the backups are not completing, please let us know.
http://support.microsoft.com/default.aspx?scid=kb;en-us;2483007
Larry Struckmeyer
Please post the resolution to your issue so that everyone can benefit
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by mpjubb Monday, July 11, 2011 6:02 AM
All replies
-
Hi:
Here is a link to the list of SBS 2011 errors that can be ignored on SBS 2011. However, if you have further evidence that the backups are not completing, please let us know.
http://support.microsoft.com/default.aspx?scid=kb;en-us;2483007
Larry Struckmeyer
Please post the resolution to your issue so that everyone can benefit
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by mpjubb Monday, July 11, 2011 6:02 AM
-
-
In the backup log, what is given as the reason for the failure? The event log may be coincidental.
Larry Struckmeyer
Please post the resolution to your issue so that everyone can benefit
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
-
I was receiving the same error on a clean install of SBS 2011 Standard with all service packs and updates from Microsoft Update.
I found the following link which mentions accounts that are enabled to create VSS copies: http://www.eventid.net/display.asp?eventid=8230&eventno=10589&source=VSS&phase=1
Using the information from there as a starting point, I did the following:
- open registry editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
- backup this key, just in case you need to restore it later
- CHANGE the value to 0 for all accounts except the NetworkService account which I left at 1
- close registry editor
- open services.msc and restart Volume Shadow Service
- retry Windows Server Backup
This time the backup was able to successfully create the volume shadow copies and continue. I am not sure yet what the consequences are for disabling these other accounts from creating VSS copies, but a successful backup is more important at the moment!
Andrew McMenimen
Concierge Computer Support - www.conciergecomputer.net
- Proposed as answer by Rick TanModerator Monday, July 11, 2011 3:37 AM
- Marked as answer by mpjubb Monday, July 11, 2011 6:03 AM
-
And the contents of the backup log(s) that give the reason for the failure? Or is it blank?
Larry Struckmeyer
Please post the resolution to your issue so that everyone can benefit
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
-
-
I was receiving the same error on a clean install of SBS 2011 Standard with all service packs and updates from Microsoft Update.
I found the following link which mentions accounts that are enabled to create VSS copies: http://www.eventid.net/display.asp?eventid=8230&eventno=10589&source=VSS&phase=1
Using the information from there as a starting point, I did the following:
- open registry editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
- backup this key, just in case you need to restore it later
- CHANGE the value to 0 for all accounts except the NetworkService account which I left at 1
- close registry editor
- open services.msc and restart Volume Shadow Service
- retry Windows Server Backup
This time the backup was able to successfully create the volume shadow copies and continue. I am not sure yet what the consequences are for disabling these other accounts from creating VSS copies, but a successful backup is more important at the moment!
Andrew McMenimen
Concierge Computer Support - www.conciergecomputer.net
This worked like a charm for me! -
I was receiving the same error on a clean install of SBS 2011 Standard with all service packs and updates from Microsoft Update.
I found the following link which mentions accounts that are enabled to create VSS copies: http://www.eventid.net/display.asp?eventid=8230&eventno=10589&source=VSS&phase=1
Using the information from there as a starting point, I did the following:
- open registry editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
- backup this key, just in case you need to restore it later
- CHANGE the value to 0 for all accounts except the NetworkService account which I left at 1
- close registry editor
- open services.msc and restart Volume Shadow Service
- retry Windows Server Backup
This time the backup was able to successfully create the volume shadow copies and continue. I am not sure yet what the consequences are for disabling these other accounts from creating VSS copies, but a successful backup is more important at the moment!
Andrew McMenimen
Concierge Computer Support - www.conciergecomputer.net
I got this warning every 4:th minute. I read that this error could be ignored but I didn't like all warnings filling up my log. Followed your link and deleted the spfarm and spsearch from the VssAccessControl (set them to zero did not help). No more warnings in my application log, thanks! Hope this doesn't crash something else..
I also got this information every third minute:
"The VSS service is shutting down due to idle timeout". Is that normal?
- Edited by joohansson Thursday, August 18, 2011 10:01 AM Not solved
-
"SERVERNAME\spsearch by change 1 to 0 fixed the backup issue" is eventually a not recommended way of fixing the issue. This will disable the spsearch writer from VSS and will not be backed up further. http://blogs.technet.com/b/sbs/archive/2011/05/24/you-must-manually-run-psconfig-after-installing-sharepoint-2010-patches.aspx is bthe right approach to fix these issues.
-
Hi Everyone
The only way that i have to make my Backups in SBS 2011 is STOP this services:
SharePoint Foundation Search V4
SharePoint VSS Writer
Stop this services make the Bakup inmediately and START the Services Again.
(Please remember that the services can start automaticaly again, so note that when the services are stopped you need to make the backup Right Now)
I do not have time to search for answers that never posted because this is the only Windows i see that has many CRITICAL errors and all are "Benign or Safe" and MSFT does not work to solve those "small" Mistakes
Hope that help!! and make a safe backups
Emilio
Emilio I. Wilde -
Hi
This worked for me on SBS2011, didnt do anything else.
Took ~15 minutes and backups now OK
Thank you Mohitkapoor
Cheers,
Mark
- Proposed as answer by SyscomDT Friday, February 24, 2012 5:04 AM
-
-