Network Management

Manual failover fails with a blank page in High Availability pool after upgrading to SolarWinds Platform 2025.2

Due to a known bug, manual failover in a High-Availability pool may fail silently (with a blank page) after upgrading to SolarWinds Platform 2025.2, but upgrading to version 2025.2.1 or applying provided workarounds can resolve the issue.

First published date

7/10/2025 7:55 AM

Last published date

7/29/2025 1:58 PM

Overview

After upgrading to SolarWinds Platform 2025.2, manually failing over a High Availability (HA) pool to the standby server fails without any error message. When initiating the manual failover and confirming the action, a spinning circle appears for about 20 seconds, then disappears without any indication of progress or completion. The failover does not occur.

Symptoms:

  • Blank page with a spinning circle for approximately 20 seconds after clicking "Force Failover."
  • No error message or confirmation that the failover succeeded or failed.
  • Manual failover action does not complete.

Product section

Network Performance Monitor

Cause

This issue occurs because of a known issue for SolarWinds Platform 2025.2, caused by a bug in which a NULL value in the Engines table prevents the system from processing the manual failover request.

Resolution

To resolve this issue, please upgrade to SolarWinds Platform 2025.2.1.  If upgrade is not possible, use the workarounds below.

Workaround 1: Manually trigger a failover using SWQL Studio from the Orion SDK

To manually trigger a failover using SWQL studio from the Orion SDK, follow the below steps:

  1. Download Orion SDK from SDK.
  2. Download the .msi file.
  3. Install SWQL Studio on the SolarWinds Platform Server. (For more details, see the THWACK post Intro to SWQL Studio.)
  4. Log in using the SolarWinds Admin password or equivalent in SWQL Studio.
  5. Navigate to Orion.HA.
  6. Double-click and expand Orion.HA.Pools entity.
  7. Right-click on Switchover.
  8. Select Invoke.
  9. Specify the pool ID of the desired pool you want to failover to.
  10. Click Invoke. 

The pool fails over to the standby server.

 

Workaround 2: Manually edit the JavaScript configuration of the SolarWinds Platform Web Console

  1. RDP to the Active Main Polling Engine.
  2. Go to C:\ProgramFiles\Solarwinds\Orion\Web\apps\apps\ha.
  3. Look for the JavaScript File "main.46e978bcacab1098.js".
  4. Open the file in Notepad as an administrator.
  5. Look for the string "n.isMultiServerFailover=i.length>".
  6. Change the value after the string from "2" to "1".
  7. Save the File.
  8. Repeat Steps 2-7 on the Standby Server.
  9. Test the Manual Force Failover in the Web Console.

The pool fails over to the standby server.

 

If workaround 2 does not address the issue, press CTRL+Shift+R to refresh the browser cache. This should allow you then to perform manual failover.