Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > WPM cannot open a new database connection using Windows Authentication

WPM cannot open a new database connection using Windows Authentication

Updated June 20, 2018

Overview

 

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

 

The following error may appear in the SEUM Business Layer log:

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

Environment

  • WPM 2.2.1
  • Orion Platform 2017.3 

Cause 

WPM 2.2.1 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 Authentication to the Orion Database

Resolution

Upgrade to WPM 2.2.2, which supports Windows SQL authentication.
 

Alternatively, use the following workaround:

  1. Make a backup copy of the SolarWinds.Orion.Common.dll file located in the SEUM install folder: C:\Program Files (x86)\SolarWinds\Orion\SEUM
  2. Copy the SolarWinds.Orion.Common.dll file in the default Orion installation folder: C:\Program Files (86)\SolarWinds\Orion
  3. Paste the DLL into the SEUM install folder: C:\Program Files (x86)\SolarWinds\Orion\SEUM
  4. Restart Orion services.

 

 

 

Last modified

Tags

Classifications

Public