| title | Availability replica is not joined | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 01/09/2019 | |
| ms.prod | sql-server-2014 | |
| ms.reviewer | ||
| ms.technology | high-availability | |
| ms.topic | conceptual | |
| f1_keywords |
|
|
| helpviewer_keywords |
|
|
| ms.assetid | 9c0d10b1-9e12-430c-83b9-ca2bd0a3afc4 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| manager | craigg |
| Policy Name | Availability Replica Join State |
| Issue | Availability Replica is not joined. |
| Category | Warning |
| Facet | Availability 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.
Note
For this release of [!INCLUDEssCurrent], 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 AlwaysOn Availability Groups (SQL Server)
Use the AlwaysOn Dashboard (SQL Server Management Studio)