Moving to a new VLAN? These are the exact steps to change the IP addresses of the Windows cluster nodes and of a SQL Server failover cluster instance.
Always On Listener Creation Fails: Attempt to Locate a Writable Domain Controller Failed
Always On listener creation can fail because the cluster cannot finish its directory work. In a 2018 client case, the same failure hit three clusters. This post shows how to read the cluster event, check DNS and directory permissions, prestage the listener object and verify the result.
HADRAG Error: Did Not Find the Instance to Connect in SqlInstToNodeMap Key
The HADRAG error ‘Did not find the instance to connect in SqlInstToNodeMap key’ kept an Always On availability group offline after unexpected failovers. The cluster log pointed to a metadata mismatch. Dropping the group on the secondary and recreating it brought it back.
Msg 5123: CREATE FILE Access Denied on TempDB After Disk Migration
Msg 5123 with operating system error 5, Access is denied, kept SQL Server from starting on a cluster after a disk migration. TempDB files could not be created on the new drive. Giving the SQL Server service account Full Control on the folders fixes it.
SQL SERVER – Event ID: 1135 – Cluster node ‘NodeName’ was Removed From the Active Failover Cluster Membership
Event ID 1135 says a cluster node was removed from the active failover cluster membership. Here is what a customer’s AlwaysOn setup taught me about it.
SQL SERVER – Unable to Start SQL Resource in Cluster – HUGE Master Database!
A client’s SQL Resource would not come online on either cluster node. The ERRORLOG showed a very slow recovery of a huge master database. Here is the fix.
SQL SERVER – Install Error: Microsoft Cluster Service (MSCS) Cluster Verification Errors – Part 3
Part 3: one more reason SQL Server setup can fail the MSCS cluster verification errors rule during install or AddNode, as seen at a client, and the fix.






