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.
SQL SERVER – Slow SQL Server 2016 Installation in Cluster: RunRemoteDiscoveryAction
A client’s SQL Server 2016 Installation in Cluster hung at RunRemoteDiscoveryAction while setup ran discovery on the other node. Here is the cause of the delay.
SQL SERVER – Unable to Failover SQL Server Instance – Error: Registry Information is Corrupt or Missing
A client could not failover SQL Server to another node: registry information is corrupt or missing. Here is how I found the right error in the logs.
SQL SERVER – Install Error: Microsoft Cluster Service (MSCS) Cluster Verification Errors – Part 2
Part 2 of my series on the MSCS cluster verification errors rule in SQL Server setup: another cause we found in Detail.txt during install or AddNode.
SQL SERVER – Install Error: Microsoft Cluster Service (MSCS) Cluster Verification Errors – Part 1
Installing a SQL Server clustered instance failed the Microsoft Cluster Service (MSCS) Cluster Verification rule. Part 1 covers the verification report cause.