Over a period, I have learned that fixing an issue is easier if we know which log we should look at and what we should search on google. Here is the situation which I was into few days back. In this blog post we will learn how to fix the error Cluster Network Name showing NETBIOS status as “The system cannot find the file specified”.
I was at client site for performance tuning exercise and they asked me if I know Windows Clustering. Of course, I can’t call myself as an expert but I at least know whatever is needed for AlwaysOn availability groups. So, I asked them the issue. They told that they are seeing Cluster Network Name in failed state as below.
We tried to move the cluster group between the nodes and tried bringing CNO online but it failed. In the CNO parameters we see the NETBIOS status as “The system cannot find the file specified”. So, I asked them to capture cluster logs.
Here is the snippet from the error log.
548020 000022c8.00004208::2016/10/08-10:38:29.991 ERR [RES] Network Name: Agent: InitializeModule, Trying to initialize Module(fb729fe4-79ea-4a0d-857e-411636879e67,Identity) when there is one already in Initialized/Idle state
548064 000022c8.00000368::2016/10/08-10:38:29.991 ERR [RES] Network Name: [NNLIB] Unable to add server name WindowsCluster to transport \Device\NetBt_If1, status 2
548083 000022c8.000038b8::2016/10/08-10:38:29.991 ERR [RES] Network Name : Online thread Failed: ERROR_SUCCESS(0)’ because of ‘Initializing netname configuration for Cluster Name failed with error 2.’
548088 000022c8.000038b8::2016/10/08-10:38:29.991 ERR [RHS] Online for resource Cluster Name failed.
548102 00001cac.00002f94::2016/10/08-10:38:29.991 ERR [RCM] rcm::RcmResource::HandleFailure: (Cluster Name)
As seen above, status 2 indicates: The system cannot find the file specified”. My search for “NetBt” was pointing to issue with “NetBIOS over TCPIP” setting. When I verified the network adapters, I noticed under WINS section NETBIOS over TCP/IP has been disabled.
Here is the screen where I changed the settings.
We have changed it to default and issue was resolved and we were able to bring the resource online.
Have you found any solution using cluster log?
Reference: Pinal Dave (https://blog.sqlauthority.com)