Availability replica is not joined

 

Published: May 17, 2016

Updated: May 17, 2016

Applies To: SQL Server 2016

Policy NameAvailability Replica Join State
IssueAvailability Replica is not joined.
CategoryWarning
FacetAvailability replica

This policy checks the join state of the availability replica. The policy is in an unhealthy state when the availability replica is added to the availability group, but is not joined properly. The policy is otherwise in a healthy state.

System_CAPS_ICON_note.jpg Note


For this release of SQL Server 2016, information about possible causes and solutions is located at Availability replica is not joined on the TechNet Wiki.

The secondary replica is not joined to the availability group. For an availability replica to be successfully joined to the availability group, the join state must be Joined Standalone Instance (1) or Joined Failover Cluster (2).

Use Transact-SQL, PowerShell, or SQL Server Management Studio to join the secondary replica to the availability group. For more information about joining secondary replicas to availability groups, see Joining a Secondary Replica to an Availability Group (SQL Server).

Overview of Always On Availability Groups (SQL Server)
Use the Always On Dashboard (SQL Server Management Studio)

Community Additions

ADD
Show: