Network Management

Orion Services will not start on HA Standby or cannot remove the High Availability Pool

The following article addresses when services do not start on a High Availability (HA) Standby or if the HA Pool cannot be removed when needed.

First published date

10/24/2018 6:43 PM

Last published date

4/19/2023 12:08 AM

Overview

The following error is displayed when starting services on an HA member:

Services will not start on HA member 

The following message is shown in the BusinessLayerHost.log file:

INFO
SolarWinds.BusinessLayerHost.BusinessLayerHostService - 
Machine is HA backup. Not waiting for SWIS, 
not starting SWIS dependent plugins.

After the above message, the Orion Services change to disable. 

This is by design on the Standby Server but not on the Main Poller. 

This can also be a problem if you are unable to remove the HA Pool. 
 

Product section

Orion Platform

Cause

The error occurs when the server was initially set up as a standby.

Resolution

** Note: Back up the registry and Database before performing these steps.**

  1. From Web Console, turn off HA
  2. Shutdown All Solarwinds services in the Orion Services Manager on  the Active (Main) Polling Engine
  3. High Availability service on all Orion servers.
  4. Truncate all HA tables: 
    TRUNCATE TABLE HA_Audit
TRUNCATE TABLE HA_FacilitiesInstances
TRUNCATE TABLE HA_PoolMemberInterfacesInfo
TRUNCATE TABLE HA_PoolMembers
TRUNCATE TABLE HA_Pools
TRUNCATE TABLE HA_ResourcesInstances

Scripts are not supported under any SolarWinds support program or service. Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.

     
  5. Check the following registry key: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolarWinds\HighAvailability\RunType
  6. Change the machine from MainPollerStandby to MainPoller.
  7. Restart High Availability Service on all Orion Servers.