Network Management

AWS Additional Website cannot load Web Console or complete Configuration Wizard after Windows/.NET updates when primary poller DNS entry is missing

On the AWS (Additional Website) node: Web Console does not load even when browsing locally (no load balancer in path). Configuration Wizard fails on: SWIS, Website, and Services steps with SolarWinds.ApiProxyFactory.TransientApiProxyException. BusinessLayerHost and related logs show: Repeated failures to open the SWIS v3 certificate endpoint on localhost:17777. Repeated errors accessing the SolarWinds Platform database in a SQL Availability Group (gcswdb-lsnr / listener).

First published date

3/25/2026 5:52 PM

Last published date

3/25/2026 5:52 PM

Overview

After monthly Windows/.NET updates, an Additional Website (AWS) server cannot load the SolarWinds Web Console and the Configuration Wizard fails on the SWIS / Website / Services steps. Logs show TransientApiProxyException, SWIS endpoint failures on net.tcp://localhost:17777/.../certificate, and SQL Availability Group errors for the SolarWinds Platform database. Root cause is a missing DNS record for the primary polling engine, combined with a temporarily unhealthy SQL AG replica.

Product section

Network Performance Monitor

Cause

  1. Missing DNS entry for the primary polling engine

    • The AWS Additional Website relies on DNS to resolve and communicate with the primary poller / SolarWinds Platform services.
    • Without a valid DNS A record for the primary poller, SWIS / Business Layer connections are unstable or fail, triggering TransientApiProxyException and SWIS endpoint errors.

  2. Unhealthy / resolving SQL Availability Group replica for SolarWinds Platform database

    • When the AWS node attempts to connect to the SolarWinds Platform database via the Availability Group(AG) listener, it connects to a replica that is not in PRIMARY or SECONDARY role, causing the AG errors above.
    • This further prevents the Business Layer from becoming healthy on the AWS node.

Result: the AWS Additional Website cannot establish reliable connections to SWIS (port 17777) and the SolarWinds Platform SQL AG, so Configuration Wizard and the local Web Console both fail.

Resolution

  1. Fix primary poller DNS resolution

    • Ensure the primary polling engine hostname (for example, GCSW01.domain) has a correct DNS A record resolving to its current IP address.
    • From the AWS node, verify:
      • ping <primary_poller_hostname>
      • nslookup <primary_poller_hostname>
    • Confirm resolution is correct and consistent with the primary poller’s actual IP.

  2. Validate and repair SolarWinds Platform SQL Availability Group state

    • With the DBA, verify the Availability Group hosting the SolarWinds Platform database:
      • Ensure the replica serving the SolarWinds environment is in a valid PRIMARY or SECONDARY role.
      • Fix any replicas in RESOLVING, FAILED, or other non-serving states.
    • Confirm that the AWS node can successfully connect to the SolarWinds Platform database via the AG listener (no “replica is not in PRIMARY or SECONDARY role” errors in logs).

  3. Repair SolarWinds Platform on the AWS Additional Website node

    On the AWS node:

    • Open Programs and Features.
    • Select the SolarWinds Platform entry and run a Repair (Core Repair).
    • After the repair, run SolarWinds Configuration Wizard:
      • Select Database, Services, and Website.
      • Let CW complete with no errors.

  4. Confirm Web Console health and re-enable load balancing

    • Browse the Web Console locally on the AWS node (e.g., https://<AWS_hostname>/Orion/) and confirm it loads normally.
    • Only after the local Web Console and CW are healthy, re-enable the AWS node on the Citrix NetScaler (or other load balancer).
    • Test the load-balanced URL (for example, https://<solarwinds.loadbalance.domain>/Orion/) to confirm normal operation.