Configuration Wizard stalls at 98.9% during Agent deployment on an Additional Polling Engine

To resolve this issue, identify the correct OrionServerID for the APE in the SolarWinds Orion database, stop the SolarWinds services on the affected APE, update AgentAutoDeploy to False, verify the database change, and then run the Configuration Wizard with the services stopped.

1. Back up the SolarWinds Platform database

Before making any database changes, take a full backup of the SolarWinds Platform database. SolarWinds recommends using SQL Server Management Studio for database backup and restore operations.

2. Open Database Manager

1. Open Database Manager from the SolarWinds Platform folder in the Windows Start menu.

2. Select Add Orion Server.

3. Expand the SQL Server shown in bold.

4. Expand the SolarWindsOrion database.

5. Right-click the database or the OrionServers table and select New Query.

The Database Manager can be used to view database and table details, perform queries, export data, and edit database values. For advanced database maintenance and backup or restore operations, use SQL Server Management Studio.

3. Identify the correct OrionServerID

The OrionServerID is the SolarWinds database identifier for a SolarWinds Platform server or APE. It is different from the Windows server ID and the NodeID.

Run the following query against the database:

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

SELECT OrionServerID,
       ServerType,
       HostName,
       NodeID,
       AgentAutoDeploy
FROM [dbo].[OrionServers]
WHERE HostName = '<Hostname>';

Record the OrionServerID returned. Do not use the example value 5 unless the query returns 5 for the affected APE.

4. Stop the SolarWinds services on the affected APE

Stop the SolarWinds services on the affected APE—the polling engine for which the database change is being made.

Keep the services stopped while applying the database update and while running the Configuration Wizard.

5. Disable AgentAutoDeploy for the affected APE

Run the following query against the database, replacing <APE_ID> with the OrionServerID returned by the identification query:

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

UPDATE [dbo].[OrionServers]
SET AgentAutoDeploy = 'False'
WHERE OrionServerID = <APE_ID>;

Confirm that the query completed successfully and that only the intended APE record was updated.

6. Verify the database change

Run the following query to verify the affected record:

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

SELECT OrionServerID,
       HostName,
       AgentAutoDeploy
FROM [dbo].[OrionServers]
WHERE OrionServerID = <APE_ID>;

The AgentAutoDeploy value should be False for the affected APE.

7. Run the Configuration Wizard

If the Configuration Wizard is required, keep the APE services stopped, run the Configuration Wizard, and restart the SolarWinds services only after the wizard completes successfully.

Additional Notes

• Always confirm the correct OrionServerID before running the update statement.

• Do not use the example value 5 unless it is the actual ID returned for the affected APE.

• Limit the update by OrionServerID so that only the intended APE record is changed.

• Keep the affected APE services stopped during the database update and Configuration Wizard execution.

• If AgentAutoDeploy becomes enabled again, capture the output of both the identification and verification queries and note the approximate time when the value changed for further investigation.

Documentation

• Configuration Wizard stalls at 98.9% during Agent deployment

• View database details and data in the Database Manager

• SolarWinds Platform requirements