Submit a ticketCall us
Home > Success Center > Web Performance Monitor (WPM) > WPM cannot open a new database connection using Windows Authentication

WPM cannot open a new database connection using Windows Authentication

Updated: March 19, 2018



WPM is no longer functioning since changing the configuration wizard to connect tot the Orion Database using Windows authentication, as supported in Core 2017.3 and later. 


The following error may appear in SEUM BusinessLayer:

ERROR SolarWinds.Orion.Common.SWEventLogging - Service was unable to open new database connection when requested.
SqlException: Login failed for user 'Domain\Username$'.
Connection string - Data Source=SQLServerHostname;Initial Catalog=SQLServerHostname;Integrated Security=True;Persist Security Info=False;Max Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120;Packet Size=4096;Application Name=SolarWinds.BusinessLayerHost@do...ll;Workstation ID=SolarwindsServerHostname

WARN  SolarWinds.Orion.Common.SWEventLogging - WPM Service [HOSTNAME] Database connection verification failed



  • WPM 2.2.1 & Orion Core 2017.3+


WPM currently does not support Windows Authentication for SQL Server so it cannot connect to the SQL instance when this property is selected during the configuration wizard. The SolarWinds.Orion.Common.dll in the SEUM directory contains old logic that can't handle Windows Auth to the Orion Database



  1. Log a case with SolarWinds Support and advise that you encountered this issue - Support will notify the Development team for tracking purposes.
  2. Please follow the below workaround:
    1. Make a backup of SolarWinds.Orion.Common.dll located in the SEUM install folder: C:\Program Files (x86)\SolarWinds\Orion\SEUM
    2. Copy the SolarWinds.Orion.Common.dll located in the Orion root install folder: C:\Program Files (86)\SolarWinds\Orion
    3. Paste it to the SEUM install folder: C:\Program Files (x86)\SolarWinds\Orion\SEUM
    4. Restart services.





Last modified