Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Orion DB on SQL AlwaysOn Cluster does not reconnect after failover

Orion DB on SQL AlwaysOn Cluster does not reconnect after failover

Created by Robert Stidman, last modified by Aileen de Lara_ret on Sep 06, 2016

Views: 350 Votes: 0 Revisions: 3

Overview

Some users have an AlwaysOn cluster with the Orion DB as a resident DB. Everything works on Node A of the AlwaysOn cluster, but when users failover to Node B SolarWinds reports an error.
If users re-run the Configuration Wizard, they can get Node B of the AlwaysOn cluster to work, but then failover back to Node A fails.

Environment

All Orion Core products

Cause 

Limitations in how we deal with SQL AlwaysOn.

Resolution

User can try to bypass Orion limitation by setting up DNS alias which points to the currently active SQL instance.
This way DNS alias will be passed to Config Wizard rather than physical instance or Availability Group listener.

 

 

 

 

Last modified

Tags

Classifications

Public