Ошибка vss 8230 - Не ошибается лишь тот, кто ничего не делает!

Remove From My Forums

Question
Hi, I am trying to get DPM2010 working to backup guest systems on a hyperV (2008 R2) cluster.

My initial backups all came back inconsistent, and running a consistency check runs for days without finishing. Servers I am backing up with an agent installed directly on
them are backing up fine.

There are no VSS errors in my logs, just the following warnings:

Event 8230, VSS

Volume Shadow Copy Service error: Failed resolving account
username with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:

Gather writers’ status

Executing Asynchronous Operation

Context:

Current State: GatherWriterStatus

Error-specific details:

Error: NetLocalGroupGetMemebers(username), 0x80070560, The specified local group does not exist.

I have checked the VssAccessControl key in the registry and there are 2 entries, one for DOMAINusername, and one for NT AuthorityNetwork Service.
The user account is a domain admin account, which was used for installing DPM.

I am curious as to whether DPM is passing the account name without the domain as the error suggests it is looking for
username rather than domainusername which would match the registry key.
I have tried adding just the username on its own to the registry but the error remained the same.

This particular server is a domain controller, however I am experiencing the same issue across 11 servers in the protection group.
I have left the consistency check running for several days and it does not finish.

Answers

James,

I think Tyler accidently gave you improper details. The proper registry setting is a KEY, not a value.

Add the following KEY on the Hyper-V host(s) you want to use the software vss provider on.

[HKLMSoftwareMicrosoftMicrosoft Data Protection ManagerAgentUseSystemSoftwareProvider]

This should force VSS to use In-Box VSS Software provider.

To verify it’s working, during a backup and see if the snapshot was created by the provider ID {b5946137-7b9f-4925-af80-51abd60b20d5}

on the Hyper-v host, run:
diskshadow
list shadows

Also, try turning off TCP Chimney on both the PS and the DPM server. It seeems the snapshot is getting created, but file transfer is getting hung. I have seen this solution fix that problem.

On 2008 the command is: Netsh int tcp set global chimney=disabled

Regards, Mike J. [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.
- Marked as answer by
  
  Sunday, December 12, 2010 9:49 PM

Summary

Error Code	Error Text	Description	Common causes
8230	Volume Shadow Copy Service error: Failed resolving account Administrator with status 1376. Check connection to domain controller and VssAccessControl registry key.	VSS requires to be authenticated with an Administrative account in order to preform its duties.	This warning is caused by an invalid account specified in the VssAccessControl registry key.

Windows Events
*****************************
Date      24/06/2016 20:14:02  
Type      Warning 
Event     8230  
Source    VSS

Volume Shadow Copy Service error: Failed resolving account Users with status 1376. Check connection to domain controller and VssAccessControl registry key. 

Operation:
  Gather writers' status
  Executing Asynchronous Operation

Context:
  Current State: GatherWriterStatus

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

Solution

To ensure success, a valid account must be specified for the VSSAccessControl registry key.

Open the registry editor.
In the Registry Editor navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSVssAccessControl
Delete the DWORD value that corresponds to the account name in the events.
Reboot the machine

Источник

I’ve been trying to knock down the number of errors appearing in my event log and I thought this was was taken care of.

Volume Shadow Copy Service error: Failed resolving account spfarm with status 1376. Check connection to domain controller and VssAccessControl registry key. I already applied the VSSREGISTRYGROUP registry modifications see «workaround» below.
After that and a reboot the error stopped but I just noticed today it returned strangely enough at 1pm. Four errors per hour, but one hour had 5 errors and another hour only had one error. First the error below, then the workaround that I
had applied below that.

Any idea what’s going on here?

Operation:

Gathering Writer Data
Executing Asynchronous Operation

Context:
Execution Context: Requestor
Current State: GatherWriterMetadata

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

You can use the following steps to workaround the issue.

1. In Active Directory Users and Computers, create a Domain Local Security Group named VSSRegistryGroup

2. Add SPFARM and SPSEARCH accounts to the VSSRegistryGroup Group

3. Run regedit

Important This
article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify
the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

4. Go to hklmsystemcurrentcontrolsetservicesvssvssaccesscontrol

5. Add Dword value of DOMAINvssregistrygroup where domain is the netbios domainname (example: CONTOSOvssregistrygroup
Note: The Domain name must be in all caps) set the value to 1

6. Remove values for domainspsearch and domainspfarm

7. Go to hklmsystemcurrentcontrolsetservicesvssdiag

8. Right click on diag and go permissions, click advanced and add VSSRegistrygroup group with Full Control.

9. Remove spsearch and spfarm accounts from the list of permissions

10. Reboot the server

Источник

To totally unlock this section you need to Log-in

On Small Business Server 2011 Standard or Windows Server 2008 R2, you may see warnings in the application event log similar to the following:

Log Name:      Application
Source:        VSS
Date:          4/11/2011 9:48:48 AM
Event ID:      8230
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      CONTOSOSERVER.contoso.local
Description:
Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.

The warnings may also reference the spfarm account.

Cause

SBS 2011 Standard Edition installs Sharepoint 2010 Foundation in SharePoint farm mode. The accounts SPfarm and SPsearch are used as service accounts for some of the Sharepoint services. In order to be able to utilize the VSS writers, the accounts must be granted access to VSS. The accounts are added by SBS to the VssAccessControl registry key but the VSS service fails to locate the accounts.

Resolution

You can use the following steps to workaround the issue.

In Active Directory Users and Computers, create a Domain Local Security Group named VSSRegistryGroup.
Add SPFARM and SPSEARCH accounts to the VSSRegistryGroup group
Run regedit.
Go to: HKLMSystemCurrentControlSetservicesvssVssAccessControl
Add DWORD value of DOMAINvssregistrygroup where domain is the netbios domain name (example: CONTOSOvssregistrygroup set the DWORD value to 1.

Note: the Domain name must be in all caps.

Remove values for domainspsearch and domainspfarm.
Go to HKLMSystemCurrentControlSetServicesVssDiag.
Right click on Diag and go Permissions, click Advanced and add VSSRegistrygroup group with Full Control.
Remove spsearch and spfarm accounts from the list of permissions.
Reboot the server

VSSAccessControl

The registry hive VSSAccessControl could list more than the default account for VSS, NETWORK SERVICE, for example Network Service and account_name).

The adding of a domain user account added to this list could raise VSS warnings, as 8230: to solve this issue you have to remove account_name from the VSSAccessControl registry hive and reboot the server.

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSVssAccessControl

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).

Источник

Remove From My Forums

Question
Here is the error, spsearch is the account I configured for the sharepoint search service. The account exist what does vss have todo with sharepoint?

Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
   Initializing Writer

Context:
   Writer Class Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Name: NPS VSS Writer

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

Источник

Question

Answers

Summary

Solution

To totally unlock this section you need to Log-in

Cause

Resolution

VSSAccessControl

Enables or prevents a writer from using a specific user account

Question

Не пропустите эти материалы по теме: