I’m not in the AlwaysOn group anymore, but your other servers think I am, and I really should be

Server not showing joined to AG but primary still shows it as joined.

 

Symptoms –

Server is still added to the availability group if you view the primary.

When browsing to the AlwaysOn High Availability from the affected server, it shows up blank

The affected server is still in the failover cluster

The affected server still has the checkbox for being added to the Availability Group (SSCM)

Troubleshooting –

Rebooted the affected server.

Failed over Cluster resource to simulate a restart, no change.

Steps to fix –

  • Stop SQL Services on the affected node.
  • From the Primary Replica, remove the affected node from the AlwaysOn Availability Group.
  • Clear the checkbox for Enable AlwaysOn Availability Groups through SSCM, hit apply.
  • Check the checkbox for Enable AlwaysOn Availability Groups through SSCM, hit apply.
  • Start SQL services on the affected node.
  • At this point, any databases that were in the availability group will need to have T-log restores, or, in my case, need to be dropped and manually re-seeded.
  • Once all databases are seeded, verify the health of the AlwaysOn Availability Group via the dashboard.

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: