Fixing Connection State Between Availability Replicas

Always On Feature

I had configured Always On on this SQL Server and soon I realized that after changing the SQL Server service account, the secondary replica went into the 'Not Connected' state.

Troubleshooting Steps

Upon investigating the logs, I discovered that the issue persisted even after restarting the secondary replica's SQL Server services. However, after restarting the primary replica's SQL Server services, the secondary replica successfully reconnected to the primary replica. This behavior suggests that the connection issue may be related to the primary replica's service account change.

Resolution

To resolve this issue, I verified that the new service account had the necessary permissions on the secondary replica. After granting the appropriate permissions, the secondary replica successfully connected to the primary replica, and the Always On configuration returned to a healthy state.

It's important to note that changing the SQL Server service account may require additional configuration steps to ensure that the new account has the necessary permissions on all replicas involved in the Always On configuration. By following these troubleshooting steps and verifying permissions, you can resolve connection issues between availability replicas and maintain a healthy Always On environment.