Network Management

Platform Connect is not able to install the Agent and gets an error in SolarWinds Platform

After creating an SaaS account, during the Agent deployment, the Platform Connect gets an error and cannot complete the Agent installation.

First published date

5/12/2026 10:58 AM

Last published date

5/12/2026 3:33 PM

Overview

 

In the Platform Connect Wizard, after typing the API Token to deploy the Agent, it gets the following error:

If you RDP the Main poller and check the C:\ProgramData\SolarWinds\Logs\PlatformBridge\platformbridge-xxxx.log, you will be able to see the following error:

INFORMATION SolarWinds.Platform.Bridge.Component.PlatformConnectSettings - The PlatformConnect is not in the expected state of 'InstallationSucceed'. Current state: 'InstallationFailed'
INFORMATION SolarWinds.Platform.Bridge.Component.MessageHandler.RetryMessageHandler - Request to SWO Public API fails with an exception 'Response status code PreconditionFailed indicates a transient failure.'. The request will be retried (3/3) in 5 seconds.

Product section

Orion Platform

Cause

The Automatic Root CA Updates is disabled in the Main poller.

You can test by running the following PowerShell commands:

1- Invoke-WebRequest -Uri 'https://agent-binaries.cloud.solarwinds.com/uams/latest/uamsclient.msi' -UseBasicParsing -OutFile '.\uamsclient.msi'

2- Get-AuthenticodeSignature -File '.\uamsclient.msi'

It should appear a Valid result.

If it appears UnknownError in Status like below, Windows is not updating the CA certificate.

Resolution

It is necessary to allow the "Automatic Root Certificates Update" on the Main poller side.

Follow the steps below:

 

  1. Open gpedit.msc by pressing Win+R, typing the command, and hitting Enter.
  2. Navigate to: Computer Configuration > Administrative Templates > System > Internet Communication Management > Internet Communication settings.
  3. Double-click "Turn off Automatic Root Certificates Update"
  4. Select Disabled to enable the updates (or "Not Configured" to revert to default behavior).
  5. Restart the Server and test the Agent installation again on Platform Connect