Network Management

SQL DR fails to reconnect to the SolarWinds Server

SQL Server failed over but does not automatically reconnect to the SolarWinds server.

First published date

4/30/2026 5:14 PM

Last published date

4/30/2026 5:14 PM

Overview

A SQL Server with AAG has failed over but failed to reconnect to the SolarWinds server despite being configured with the correct listener.

Product section

Network Performance Monitor

Cause

Failover mode on the AG set-up was not set to Automatic

Resolution

Initial checks:

Make sure that both AG servers are UP
For this issue, AG is on a single subnet set-up
On the Configuration Wizard, make sure that the customer is using the AG Listener DNS

1) RDP to the SQL Server and open SQL Server Management Studio

2) In Object Explorer, find the primary replica of the SolarWinds DB Server.

3) Expand the Always On High Availability node > Right-click the availability group and select Properties.

4) In the shown dialog box, there should be a Failover Mode column. If it's set to Manual, change it to Automatic; otherwise, whenever the primary replica fails, it will get stuck and wait until a DBA swaps it over manually, or if the primary replica recovers.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.