After a cluster rebuild, adding a replica failed: The specified instance is hosted by a system that is not a Windows Server Failover Cluster node. Here is the fix.
SQL SERVER – Availability Group Seen in SSMS but missing in Cluster Manager. What’s Wrong?
A client’s availability group showed in SSMS, but no role appeared in Failover Cluster Manager. Here is the sequence of steps that causes this and what to do.
SQL SERVER – Always On Availability Group Listener Missing in SSMS but Working Fine in Failover Cluster Manager
My client’s AG listener worked fine in Failover Cluster Manager, yet SSMS showed nothing. Here is what causes a listener missing in SSMS and the fix.
SQL SERVER – FIX: Msg 41105: Failed to Create the Windows Server Failover Clustering (WSFC) Resource With Name and Type ‘SQL Server Availability Group’
Creating an availability group failed with Msg 41105: Failed to create the WSFC resource with type ‘SQL Server Availability Group’. Here are ways to fix it.
Set-ClusterParameter Error: ProbePort Does Not Exist on the Cluster Object
The Set-ClusterParameter error said Parameter ‘ProbePort’ does not exist on the cluster object. I hit it while setting up a probe port for an Always On listener in Azure. Two wrong values in my script were the cause, and fixing both let the script run.
AlwaysOn Queries Stuck on HADR_AR_CRITICAL_SECTION_ENTRY Wait
AlwaysOn queries stuck on HADR_AR_CRITICAL_SECTION_ENTRY followed a short loss of cluster quorum at a client site. Every change to the availability group waited. Setting failover to manual and restarting both replicas cleared the wait.
SQL SERVER – Cluster Resource ‘AGName’ of type ‘SQL Server Availability Group’ in Clustered Role ‘AGName’ Failed
Configuring an availability group is easy; trouble starts when the cluster breaks. Here I fix a failed cluster resource of type SQL Server Availability Group.