An AlwaysOn resource would not come online, and the cluster log showed sp_server_diagnostics failing with error 297, no permission. Here is the fix.
SQL SERVER – AlwaysOn Join Error – Msg 1408, Level 16 – The Remote Copy of Database “SQLAUTH” is Not Recovered Far Enough to Enable Database Mirroring or to Join it to the Availability Group
I do provide consultancy services for deployments, including AlwaysOn availability group deployments. AlwaysOn Join Error.
SQL SERVER – FIX: Msg 35250, Level 16, State 7 – The Connection to the Primary Replica is Not Active. The Command Cannot be Processed
Joining a database to an availability group failed with Msg 35250: the connection to the Primary Replica is not active. Here is why and how to fix it.
Error 19407: The Lease Between the Availability Group and the Cluster Expired
Error 19407 means the lease between an availability group and the Windows Server Failover Cluster has expired, and the group goes to Resolving. Here is what each ERRORLOG line says and what to look at first.
SQL SERVER – AlwaysOn Listener Error – The WSFC Cluster Could Not Bring the Network Name Resource With DNS Name ‘DNS name’ Online
Creating an AlwaysOn listener failed: the WSFC cluster could not bring the Network Name resource with DNS name online. Why it happens and how to fix it.
SQL SERVER – Availability Group Missing or Deleted Automatically?
Investigate an availability group missing from SSMS by comparing SQL metadata, replica state and cluster logs before choosing a recovery procedure.
SQL SERVER – FIX : Msg 35295, Level 16 – Log Backup For Database ‘DBName’ on a Secondary Replica Failed
During load testing, a log backup on a secondary replica failed with Msg 35295 because the last backup LSN was ahead of the redo LSN. Here is why.