availability-replica-is-disconnected.md

title	Availability replica is disconnected in an availability group
description	Identify possible causes for why a replica is disconnected within an Always On availability group.
ms.custom	seodec18
ms.date	05/17/2016
ms.prod	sql
ms.reviewer
ms.technology	high-availability
ms.topic	troubleshooting
f1_keywords	sql13.swb.agdashboard.arp2connected.issues.f1
helpviewer_keywords	Availability Groups [SQL Server], policies
ms.assetid	1a2162d3-54fb-4356-b349-effbdc15a5a4
author	MashaMSFT
ms.author	mathoma

Availability replica is disconnected within an Always On availability group

[!INCLUDE SQL Server]

Introduction

Policy Name	Availability Replica Connection State
Issue	Availability replica is disconnected.
Category	Critical
Facet	Availability replica

Description

This policy checks the connection state between availability replicas. The policy is in an unhealthy state when the connection state of the availability replica is DISCONNECTED. 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 disconnected on the TechNet Wiki.

Possible Causes

The secondary replica is not connected to the primary replica. The connected state is DISCONNECTED. This issue can be caused by the following:

• The connection port might be in conflict with another application.

• The encryption type or algorithm is mismatched.

• The connection endpoint has been deleted or has not been started.

• The transport is disconnected.

Possible Solutions

Following are possible solutions for this issue:

• Check the database mirroring endpoint configuration for the instances of the primary and secondary replica and update the mismatched configuration.

• Check if the port is conflicting, and if so, change the port number.

See Also

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