Network Management

Orion Module Engine crashing with Fatal: The referenced account is currently locked out and may not be logged on to

Orion Module Engine crashes during startup. FATAL SolarWinds.BusinessLayerHost.BusinessLayerHostService - Failed to initialize: System.ComponentModel.Win32Exception (0x80004005): The referenced account is currently locked out and may not be logged on to. The referenced account is currently locked out and may not be logged on to

First published date

1/19/2021 4:27 PM

Last published date

8/26/2025 9:21 PM

Overview

During service startup, the Orion Module Engine service crashes nearly immediately. Checking the Business Layer logs present the error entry below.

C:\ProgramData\SolarWinds\Logs\Orion\BusinessLayerHost.log

ERROR SolarWinds.Orion.Common.SWEventLogging - Service was unable to open new database connection when requested. Win32Exception: The referenced account is currently locked out and may not be logged on to FATAL

SolarWinds.BusinessLayerHost.BusinessLayerHostService - Failed to initialize: System.ComponentModel.Win32Exception (0x80004005): The referenced account is currently locked out and may not be logged on to

Product section

Orion Platform

Cause

SQL user is locking out.

Resolution

Check the SQL logs to identify the host that is locking out the service account. 

  1. Launch SQL Server Management Studio
  2. Connect to the SQL server
  3. Go to Management > SQL Server Logs > Current
  4. Verify the latest log entry at the top of this list. 

  1. Take action based on the event message.

Common causes:

  • SolarWinds Platform services running on an older polling engine that was migrated from.
  • Untrusted domain between SQL and SolarWinds Platform host.