Three clients hit the same issue after adding node at a DR site to an AlwaysOn cluster: disks on the original servers went offline. Here is what to watch for.
SQL SERVER – FIX: Msg 35250 – The Connection to the Primary Replica is Not Active. The Command Cannot be Processed
A reader still got Msg 35250 after my first post, with no mirroring login error in the ERRORLOG. Here are the endpoint and service account checks I asked for.
SQL SERVER – Can I Delete Always On Availability Groups Initial Sync Folder?
Can you delete the shared folder used for the initial sync of Always On availability groups? A client asked, and yes, you can remove it without any impact.
SQL SERVER – sp_server_diagnostics – The User Does Not Have Permission to Perform this Action. (297)
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.
SQL SERVER – The Lease between Availability Group ‘PRODAG’ and the Windows Server Failover Cluster has Expired
The lease between availability group and the Windows Server Failover Cluster has expired: a common error. Here is what each ERRORLOG line means.