Network Management

Server Error in '/' Application when launching the SolarWinds Platform Web Console in a high availability pool

This article helps users resolve the issue of being unable to login to the Web Console due to the Main Platform Server incorrectly showing as a standby server in a High Availability (HA) environment.

First published date

1/6/2026 10:30 PM

Last published date

1/6/2026 10:30 PM

Overview

After renaming the Main Polling Engine, users experience a web-based pop-up error preventing login to the Web Console. This occurs because the system mistakenly identifies the Main Poller as a standby server in the HA configuration.
Server Error in '/' Application. There was no endpoint listening at net.tcp://<hostname>:17777/orion/licensing/featureserver that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
In the BusinessLayerHost.log, the following message appears:
INFO Message: 2025-10-14 10:56:55,090 [8] INFO SolarWinds.BusinessLayerHost.BusinessLayerHostService - Machine is HA backup. Not waiting for SWIS, not starting SWIS dependent plugins.
 

Product section

Network Performance Monitor

Cause

  • The issue is caused by HA database tables being populated.  The customer does not have an HA setup and only uses a single Main Poller.
  • This incorrect HA data causes the Main Poller to be marked as "MainPollerStandby" in the Windows registry, leading to service startup issues and login failures.
  • This problem can potentially affect any version of the SolarWinds Platform product.

Resolution

Resolution

  1. Stop the SolarWinds High Availability service via Windows Services on the affected server.

  2. Open the Registry Editor and navigate to:

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SolarWinds\HighAvailability

  3. Modify the RunType registry key value from "MainPollerStandby" to "MainPoller".

  4. Using the SolarWinds Database Manager, execute the following SQL queries to truncate HA tables:

-- 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.

TRUNCATE TABLE [dbo].[HA_Audit]
TRUNCATE TABLE [dbo].[HA_FacilitiesInstances]
TRUNCATE TABLE [dbo].[HA_PoolMemberInterfacesInfo]
TRUNCATE TABLE [dbo].[HA_PoolMembers]
TRUNCATE TABLE [dbo].[HA_Pools]
TRUNCATE TABLE [dbo].[HA_ResourcesInstances]


Note: Truncating these tables will remove all existing HA pool configurations.

  1. Restart all SolarWinds Platform services.

  2. Re-enable and start the SolarWinds High Availability service.

  3. Monitor the log file at:

    C:\ProgramData\SolarWinds\Logs\Orion\BusinessLayerHost.log

    Wait for the message: "All Plugins Started".

  4. Once the services are fully started, you should be able to log in to the Web Console successfully.

If you continue to experience issues, verify that the registry and database entries correctly reflect the active Main Poller status and that no orphaned HA configurations exist.

See How to rebuild SolarWinds High Availability for more information.