Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Network Performance Monitor (NPM) > Orion High Availability: Create HA Pool button is missing

Orion High Availability: Create HA Pool button is missing

Updated June 8, 2017


This article provides information and steps to resolve the issue where the NPM server High Availability (HA) Deployment Summary does not display options to create an HA Pool.

The Orion HA "SET UP HIGH AVAILABILITY POOL" button is missing from HA Summary page:

SolarWinds Orion Demo - High Availability Deployment Summary


NPM 12.0.1 and later


This issue occurs when the registry is incorrectly set on the secondary HA member. For example:

  • The secondary HA member is installed as another primary polling engine and its registry RunType is set to MainPoller.
  • There is no record of the secondary HA member in the OrionServers table, which is crucial in the model for the HA summary.


Fix the registry HA keys and clean up the HA tables.

  1. Stop all the Orion services on the standby server via Orion Service Manager.
  2. Stop the High Availability service via services.msc and on other non-standby Orion servers.
  3. Remove the standby server from the Engines table using the delete SQL statement.
  4. Remove respective records from the EnginesProperties table and verify that there are no orphaned junk records.
  5. Remove the standby server from the Websites table.
  6. On secondary HA member, update its RunType to MainPollerStandby:
  7. In the following code, provide the orphaned server host name instead of ServerHostname, and run the script in SQL Management Studio or in the Database Manager:
    /****** Script for deleting obsolete pool members ******/
    DECLARE @HostnameToClear nvarchar(max)
    SET @HostnameToClear = 'ServerHostname'
    --DELETE FROM Engines WHERE ServerName = @HostnameToClear
    --DELETE FROM EngineProperties WHERE EngineID NOT IN (SELECT EngineID FROM Engines)
    DELETE FROM Websites WHERE ServerName LIKE ('%' + @HostnameToClear +'%')
    --DELETE FROM OrionServers WHERE HostName = @HostnameToClear
    DELETE FROM HA_PoolMembers WHERE HostName NOT IN (SELECT HostName FROM OrionServers)
    DELETE FROM HA_ResourcesInstances WHERE PoolMemberId NOT IN (SELECT PoolMemberId FROM HA_PoolMembers)
    DELETE FROM HA_FacilitiesInstances WHERE (RefId like '%' + @HostnameToClear + '%')
    DELETE FROM HA_PoolMemberInterfacesInfo WHERE PoolMemberId NOT IN (SELECT PoolMemberId FROM HA_PoolMembers) 

    The script deletes references to the orphaned server from the database.

  8. If you want to continue using the server as a High Availability server, run the Configuration wizard on the server. The Configuration Wizard provides information about the server into the OrionServers table.
  9. Restart Orion High Availability Services on the Orion servers via services.msc.

You should now be able to see the "SET UP HIGH AVAILABILITY POOL" button when you open the High Availability Deployment Summary page and proceed to create an HA Pool.



Last modified