SQL SERVER – Network Name resource fails to come online in a Windows Server 2008 R2 Failover Cluster

Even if you are a DBA, sometime you need to deal with issues which are not related to SQL Server. It is not by design, but this is part of our job description. It is always interesting to troubleshoot such issues and find a solution. I always think, sharing such strange troubleshooting – it will help those who get into this problem, not understanding what is happening behind the scenes. Let us learn about in this module Windows Server 2008 R2 Failover Cluster.

I always believe that searching the right error message on the internet would lead to a solution. My client, has added a new disk to the cluster nodes after shutting them down simultaneously. The cluster network name for the groups in the cluster and the associated resources were in a failed/offline state after this.

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          <Date> <Time>
Event ID:      1207
Task Category: Network Name Resource
Level:         Error
Keywords:
User:          SYSTEM
Computer:      <MachineName>
Description:
Cluster network name resource ‘SQL Network Name (SQL Server)’ cannot be brought online. The computer object associated with the resource could not be updated in domain ‘sqlauthority.com’ for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.

Since event log does not show most of the information about cluster internal operations, I have generated cluster log

SQL SERVER – Steps to Generate Windows Cluster Log?

Here is what we saw. I have removed date time from below for clarity.

• INFO [RES] Network Name <SQL Network Name (SQL SERVER)>: FQDN name SQL SERVER.sqlauthority.com removal with LSA was successful
• WARN [RES] Network Name <SQL Network Name (SQL SERVER)>: Trying to remove credentials for LocalSystem returned status C0000225, STATUS_NOT_FOUND is a non-critical failure for a remove operation
• INFO [RCM] HandleMonitorReply: TERMINATERESOURCE for ‘SQL Network Name (SQL SERVER)’, gen(37) result 0.
• INFO [RCM] TransitionToState(SQL Network Name (SQL SERVER)) [Terminating to Failed]–>Failed.
• INFO [RCM] rcm::RcmGroup::UpdateStateIfChanged: (cgSQL SERVER, Pending –> Failed)
• INFO [RES] Network Name <Cluster Name>: Getting a virtual computer account token.
• INFO [RES] Network Name <Cluster Name>: Logon failed so priming local KDC cache to \\AUTHDC001.sqlauthority.com for domain sqlauthority.com, status = 0 .
• INFO [RES] Network Name <Cluster Name>: Logon failed so priming local KDC cache to \\AUTHDC001.sqlauthority.com for domain tportal, status = 0 .
• ERR [RES] Network Name <Cluster Name>: Unable to Logon. winError 1326
• ERR [RHS] Error 1326 from ResourceControl for resource Cluster Name.

In above we see some WARN (for warning) and some ERR (for Error).

Error 1326 = “The user name or password is incorrect”

I search at various places on the internet and found that this can be fixed by repair of computer object. Below is the screenshot for that.

After doing repairs, we were able to bring the NN online. Have you ever faced a similar situation? Does this make sense. Have you ever done this activity, what was the scenario. Please let me know via comments.

Reference: Pinal Dave (https://blog.sqlauthority.com)