VSS error: Failed resolving account Administrator with status 1376

On my domain controllers, the following errors occurred in my eventlog:

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

  1. Open your registry
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
  3. 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).

Leave a Reply

6 Comments on "VSS error: Failed resolving account Administrator with status 1376"

Notify of
avatar
Sort by:   newest | oldest | most voted
John Cruz
Guest

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.

Parnell
Guest

It works!

Petr Kasl
Guest

Thank You,

it works!

Jan Peter Koen
Guest

This worked! Thanks.

Larry
Guest

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?

Jin Pen Fa
Guest

Great! Thanx! No problems found so far, so I guess this is a harmless, but helpful solution!

wpDiscuz