Network Management

Configuration Wizard fails with "The referenced account is currently locked out" error after SQL service account password rotation

This article explains how to resolve a Configuration Wizard failure caused by stale SQL service account credentials cached in the SWNetPerfMon.db file after a service account password rotation, resulting in an Active Directory account lockout error.

First published date

4/23/2026 10:52 PM

Last published date

4/23/2026 11:09 PM

Overview

After the SQL database service account password is rotated at the Active Directory or SQL level, the SolarWinds Configuration Wizard may fail at the final stage with the following error:

The referenced account is currently locked out and may not be logged on to.

The following Configuration Wizard tasks fail:

  • Create Engine Record — FAILED

  • Updating MenuItems Table — FAILED

  • Orion Website Maintenance Account — FAILED

The SolarWinds Web Console becomes inaccessible, returning the same lockout error. The issue persists even when a new SQL service account is supplied in the Configuration Wizard.

Error Message

ConfigurationWizard.log:

DEBUG NetFlowConnectionStringStore - FSDB connection string from Orion database:
Data Source=tcp:<SQLServer>;Initial Catalog=SolarWindsFlowStorage;
Integrated Security=True;User ID=DOMAIN\OldServiceAccount;Password=***;
Encrypt=True;TrustServerCertificate=True

DEBUG ImpersonationContext - LogonType: LOGON32_LOGON_NETWORK_CLEARTEXT will be used.

ERROR ExceptionLogger - System.Net.Sockets.SocketException (0x80004005):
An existing connection was forcibly closed by the remote host
  at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
  at SolarWinds.ConfigurationWizard.Common.DatabaseHelper.GetServerInstanceList(String serverName)

Product section

Network Performance Monitor

Cause

When the SQL service account password is rotated, the old credentials remain cached in the SWNetPerfMon.db file located at <Volume>\Program Files\SolarWinds\Orion\. This file stores the database connection strings used by SolarWinds, including the NetFlow Flow Storage Database (FSDB) connection string.

Because the old account credentials are still present in SWNetPerfMon.db, the Configuration Wizard continues to attempt authentication using the locked-out account — even when new credentials are provided during the wizard. This triggers a Windows-level Active Directory account lockout, causing the wizard to fail.

Resolution

To resolve this issue, delete the stale SWNetPerfMon.db file, then re-run the Configuration Wizard with the new service account credentials. Perform the following steps on the Main Polling Engine (MPE) first, then repeat on all additional polling engines (APEs) and additional web servers (AWS).

Step 1 — Stop SolarWinds services

Open the SolarWinds Platform Service Manager and stop all SolarWinds services.

Step 2 — Back up and delete the SWNetPerfMon.db file

  1. Navigate to <Volume>\Program Files\SolarWinds\Orion\.

  2. Locate the file SWNetPerfMon.db.

  3. Copy the file to a backup location (e.g., the Desktop).

  4. Delete the original SWNetPerfMon.db file from the Orion directory.

Note: The Configuration Wizard will regenerate this file with the correct credentials when re-run.

Step 3 — Re-run the Configuration Wizard

  1. Open the Configuration Wizard as Administrator.

    • Go to Start > SolarWinds Platform > Configuration Wizard.

    • Right-click and select Run as administrator.

  2. On the Database Settings page, enter the new SQL service account credentials.

  3. Allow the wizard to complete fully (Database, Website, and Services).

Step 4 — Repeat on all APEs and AWS

Repeat Steps 2 and 3 on every additional polling engine (APE) and additional web server (AWS) in the environment.

Step 5 — Verify

  1. Confirm the SolarWinds Web Console is accessible.

  2. Verify that all SolarWinds services are running via the SolarWinds Platform Service Manager.

  3. Confirm polling has resumed normally.