Event 8230 Vss Volume Shadow Copy Service Error
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums event id 8230 vss failed resolving account administrator with status 1376 Answered by: How do i resolve Event ID: 8230
Event Id 8230 Server 2008 R2
Source VSS with SBS 2011? Windows Small Business Server > Small Business Server Question 1 hkey_local_machine\system\currentcontrolset\services\vss\vssaccesscontrol Sign in to vote We're having a problem with one of the volumes not backing up. It apears to be linked to the VSS
Event Id 8230 Vss Windows 2008 R2
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. vssaccesscontrol registry key 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 Thursday, July 07, 2011 8:18 AM Reply | Quote Answers 5 Sign in to vote 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, Idid the following: open registryeditor and navigate toHKEY_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 clos
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free
Create A Domain Local Security Group
for subscribers Event ID: 8230 Source: VSS Source: VSS Type: Warning Description:Volume Shadow
Event Id 14 Sharepoint Foundation Search
Copy Service error: Failed resolving account account_name with status 1376. Check connection to domain controller and VssAccessControl registry key. Error-specific details: me2537096 Error: NetLocalGroupGetMemebers(account_name) 0x80070560 The specified local group does not exist. English: Request a translation of the event description in plain English. Comments: Anonymous If this is happening on SBS 2011 Standard, here is the fix: https://social.technet.microsoft.com/Forums/en-US/7c55c3c6-e139-4787-be36-9feb1a351fd1/how-do-i-resolve-event-id-8230-source-vss-with-sbs-2011?forum=smallbusinessserver ME2537096. x 18 Anonymous Problem was resolved by reconfiguring Sharepoint 2010. Go to start, Sharepoint 2010 and launch the Sharepoint 2010 Products Configuration. Follow the steps and all works fine again. x 45 Anonymous In the case of SBS 2011, don't make any changes, this is a normal event and should be ignored. See ME2483007. x 58 Markus H. In my case I had two identical domain controllers running Windows Server http://www.eventid.net/display-eventid-8230-source-VSS-eventno-10589-phase-1.htm 2008 R2. Each time a Windows Server Backup starts I received VSS event 8230. I've found a registry hive VSSAccessControl, where two accounts were listed (NetworkService, account_name). To solve this issue I had to remove account_name from the VSSAccessControl registry hive and reboot the server. \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl As per Microsoft: Enables or prevents a writer from using a specific user account. In order for any writer to use the VSS infrastructure, the writer must run under an account that is a member of the local Administrators or Backup Operators group on the local computer. For example, a writer running under the Local System account meets this requirement. This is true for the vast majority of writers. You can, however, enable a writer to use a specific user account by adding the appropriate registry entry. You can also prevent a writer from using a specific user account. To enable a writer to use a specific user account, add a REG_DWORD entry with the name equal with the user name. Set the value of the registry entry to 1 (one). To prevent a writer from using a specific user account, add a REG_DWORD entry with the name equal with the user name. Set the value of the registry entry to 0 (zero). See T787
101 FREE Hyper-V Tools A Free Configurable PowerShell Script for Hyper-V Export Our favorite Hyper-V & Windows Server Blogs TechSupport Browse: http://www.altaro.com/hyper-v/sbs-2011-backups-failing-vss-error-0x800423f3-event-id-8230-spfarm-spsearch/ Home / SBS 2011 Backups Failing - VSS Error 0x800423F3 – Event http://www.itexperience.net/2011/09/02/vss-error-failed-resolving-account-administrator-with-status-1376/ ID 8230 (spfarm, spsearch) by Altaro Software in TechSupportTags: event viewer, hyper-v, vss SBS 2011 Backups Failing - VSS Error 0x800423F3 – Event ID 8230 (spfarm, spsearch) 27 Jan 2012 by Altaro Software 7 TechSupport A customer using Altaro Hyper-V Backup on Windows 2008 event id R2 Enterprise SP 1 contacted us because attempts to back up a virtual machine that had Small Business Server 2011 (SBS) installed were failing due to a VSS error.We began troubleshooting by collecting the Altaro Error Logs, Windows Application and System Event Logs, and a dump of the VSS Writers and Providers from the Hyper-V host.From the event id 8230 Altaro Error logs, we saw that the VSS request was failing with the error VSS_E_WRITERERROR_RETRYABLE (0x800423F3L). Normally, the cause of VSS errors can be determined by checking the Windows event logs, but in this case, those contained no clues. That typically means that the underlying problem is within the virtual machine itself.We accessed the Application and System Event Logs from the SBS 2011 virtual machine itself. The Application event log held many VSS warnings, verifying that the problem stemmed from a condition within the SBS 2011 VM.All VSS warnings had the same ID – Event ID 8230.Event ID: 8230Source: VSSLevel: WarningVolume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.Operation:Gathering Writer DataExecutingAsynchronous OperationContext:Execution Context: RequestorCurrent State: GatherWriterMetadataError-specific details:Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.The pivotal item in the event description is the reference to the VssAccessControl registry key. We retrieved a copy of the customer’s “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\VssAccessControl” registry key and immediately saw that, apart from the "NT Authority\NetworkS
VSS Event ID: 8230 Task Category: None Level: Warning Computer: DomainController1 Description: Volume Shadow Copy Service error: Failed resolving account Administrator 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(Administrator), 0x80070560, The specified local group does not exist. and: Log Name: Application Source: VSS Event ID: 8230 Task Category: None Level: Warning Computer: DomainController1 Description: Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key. Error-specific details: Error: NetLocalGroupGetMemebers(Administrator), 0x80070560, The specified local group does not exist. The events appeared in my eventviewer after creating backups with Tivoli Storage Manager (TSM). Although the backup procedure was running fine, the events were annoying. So here's how to fix it: Open your registry Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl Delete the DWORD-key that corresponds to the account name in the events. In my case, it was Administrator (Failed resolving account Administrator with status 1376). tivoli tsm vss VssAccessControl 6 thoughts on “VSS error: Failed resolving account Administrator with status 1376” John Cruz says: July 7, 2015 at 12:36 am Be sure to hang around after you make this change, my DC decided to turn itself off after encountering other errors once I killed this reg key. Reply Parnell says: February 16, 2015 at 2:22 pm It works! Reply Petr Kasl says: December 22, 2014 at 8:00 pm Thank You, it works! Reply Jan Peter Koen says: January 29, 2014 at 3:46 pm This worked! Thanks. Reply Larry says: June 3, 2013 at 6:38 pm That will get rid of the error but what if that registry key is supposedly the solution to another problem that you have with VSS. In my case that was supposed to be the solution but the adminsitrator user isn't resolving. I did try doing the fully qualified name, administrator@domain.local and didn't get an error. has anyone tried this? Reply Jin Pen Fa says: September 2, 2011 at 10:44 am Great! Thanx! No problems found so far, so I guess this is a harmless, but helpful solution! Reply Leave a Reply Cancel reply Your email address will not be published.Comment Name Email Website Post navigation