Availability replica is disconnected

Availability replica is disconnected

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.

 

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.
Sort by: Published Date | Most Recent | Most Useful
Comments
  • How do you checking the database mirroring endpoint configuration? How do you check if the port is conflicting?

  • How do you checking the database mirroring endpoint configuration? How do you check if the port is conflicting?

  • which application is using my port

    netstat -o -n -a | findstr 0.0:5022

    This will give you an output like this

    netstat -o -n -a | findstr 0.0:5022

     TCP    0.0.0.0:5022           0.0.0.0:0              LISTENING       XXXX

    XXXX is the PID of the program you should check.

  • ok netstat shows "sqlservr" now what? any chance you can go through an example of this?

    no ports appear to conflict with 1433 or 5022...

Page 1 of 1 (4 items)