Centralized Upgrade Shows APE and AWS as "Not updatable" in the SolarWinds Platform

2/12/2026 5:26 PM

2/12/2026 5:52 PM

Applies to

• SolarWinds Platform with Additional Polling Engines (APEs) and/or Additional Web Servers (AWSs)

• Environments where High Availability (HA) was previously configured or partially removed

Symptoms

In Centralized Upgrade, one or more APEs or AWSs show status “No updatable”.
For at least one affected APE, the Upgrade/Pre‑flight screen shows an error similar to:

Server <poller_name> cannot be upgraded. Unable to calculate the upgrade path for server <poller_name> due to product inconsistencies between the main polling engine and <poller_name>.

Additional observations:

• Main Polling Engine(s) appear as Connected and updatable.

• APEs/AWSs appear as Not updatable or disconnected even though services are running.

• The HA_PoolMembers view in the SolarWinds Platform database may show two main polling engines marked Active or stale HA data for old pool members.

Network Configuration Manager

The Centralized Upgrade service relies on consistent HA/role metadata in the SolarWinds Platform database to determine upgrade eligibility for each polling engine and web server.

If HA was previously configured and later removed or partially disabled, stale HA and limitation records can remain in the database (for example in HA_Pools, HA_PoolMembers, HA_ResourcesInstances, Limitations, etc.). These inconsistencies can cause:

• The upgrade service to see conflicting main poller references. From HA_PoolMembers table the 2xMPEs showing MainPoller on the PoolMemberType column.

• In addition, in the registry of both servers showing MainPoller in RunType for High Availability.

• APEs/AWSs to be treated as invalid or out‑of‑sync with the main poller.

• Resulting “Not updatable” status and the “Unable to calculate the upgrade path” error.

Important

• Full Back up the SolarWinds Platform database before making any changes.

• The following steps include database changes. They should be performed by or under the guidance of a database administrator and/or SolarWinds Support.

Step 1 – Verify and disable HA at the application layer

1. If HA is currently configured, disable HA from the SolarWinds web console where possible. - https://documentation.solarwinds.com/en/success_center/orionplatform/content/ha_configure_ha_settings.htm

2. Follow the documented procedure to disable HA from the command line (if applicable):

   • Disable HA in the command prompt

Step 2 – Stop HA and SolarWinds Platform services on affected servers only

Perform the following on affected Main Polling Engines, and/or APEs:

1. Stop the High Availability (HA) service via Windows Services.

2. Open SolarWinds Platform Service Manager on each server and:

   • Stop all SolarWinds Platform/module‑related services, websites (applicable only in MPE), and dependencies  via SolarWinds Platform Service Manager 

   • Wait until all SolarWinds services are stopped.

Step 3 – Clean up HA and limitation data in the SolarWinds Platform database

Using Database Manager or SQL Server Management Studio, connect to the SolarWinds Platform database and run the following script in order:

-- Standard script disclaimer:
-- 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.

-- Normalize and clean up Limitations definitions
UPDATE [dbo].[Limitations]
SET WhereClause = REPLACE(
                      REPLACE(
                          REPLACE(CAST(WhereClause AS varchar(max)), '( (', ' ( ( '),
                          '((', ' ( ( '
                      ),
                      '))', ' ) ) '
                  );

DELETE FROM [dbo].[Limitations]
WHERE WhereClause = '1=1';

DELETE FROM [dbo].[LimitationSnapShots];

-- Clear container and pending notification snapshots that can reference stale members
DELETE FROM [dbo].[ContainerMemberSnapshots];
DELETE FROM [dbo].[PendingNotifications];

-- Clean up subscriptions not pointing to HTTP endpoints
DELETE FROM [dbo].[SubscriptionTags];
DELETE FROM [dbo].[Subscriptions]
WHERE EndpointAddress NOT LIKE 'http%';

-- Clear active installer sessions that can block upgrades
DELETE FROM SWA_InstallationSession WHERE IsActive = 1;

Clean up HA:

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

DECLARE @Hostname nvarchar(max)

SET @Hostname = 'NAME'

DECLARE @PMID int = (SELECT TOP 1 [PoolMemberId] FROM [HA_PoolMembers] WHERE [HostName] = @Hostname)

DELETE FROM [HA_FacilitiesInstances] WHERE [PoolMemberId] = @PMID

DELETE FROM [HA_PoolMemberInterfacesInfo] WHERE [PoolMemberId] = @PMID

DELETE FROM [HA_ResourcesInstances] WHERE [PoolMemberId] = @PMID

DELETE FROM [HA_PoolMembers] WHERE [PoolMemberId] = @PMID

Step 4 – Check Engines table

On Engines table, make sure that the ServerName column and IP address column is showing the HA active servername and its IP address. Not showing showing the correct details or having 2xPrimay server.

If the Engines table is showing both the expected Active and Standby server. Do the below:

1. from Engines table > click execute query button.

2. click Enable table editing

3. right click on the row for the server/engine to be deleted

If the Engines table is showing the wrong active engine. Do the below:

1. from Engines table > click execute query button.

2. click Enable table editing

3. Double click on the Servername you need to change and replace it with correct Servername and hit enter to save it. Do the same when changing the IP.

 

Note: Please also check any wrong entries or duplicate entries on Websites table. Thank you!

Step 5 – Correct the InstallType and RunType of the server.

From the registry "HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > SolarWinds > High Availability"
**On the Active Primary polling engine, both InstallType and RunType values must be MainPoller.
**On the Standby Primary polling engine, both InstallType and RunType values must be MainPollerStandby.
**On the Active Additional polling engine, both InstallType and RunType values must be AdditionalPoller.
**On the Standby Additional polling engine, both InstallType and RunType values must be AdditionalPollerStandby. 

Step 6 – Start services and validate Centralized Upgrade

On all pollers that is expected to be the Active server in relation to HA:

1. Start the High Availability (HA) service via Windows Services.

2. Open SolarWinds Platform Service Manager on each server and:

   • Start all SolarWinds Platform/module‑related services, websites (applicable only in MPE), and dependencies  via SolarWinds Platform Service Manager 

On all pollers that is expected to be the Standby server in relation to HA:

1. Start the High Availability (HA) service via Windows Services.

2. Open SolarWinds Platform Service Manager on each server and:

   • Start all SolarWinds Platform/module‑related services, websites (applicable only in MPE), and dependencies  via SolarWinds Platform Service Manager 

After all services are running:

1. Open the SolarWinds web console.

2. Navigate to Settings > All Settings > SolarWinds Platform > Centralized Upgrade.

3. Confirm that:

   • Main Poller is Connected and upgradable.

   • All APEs and AWSs now show as Connected with valid upgrade options (no longer “No updatable”).

4. Re‑run pre‑flight checks and confirm that the previous error:

   • “Unable to calculate the upgrade path…” no longer appears for any APE/AWS.