Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Database Performance Analyzer (DPA) > Failed to Register SQL Instance (failed to authenticate monitoring user) error when you try to register a database

Failed to Register SQL Instance (failed to authenticate monitoring user) error when you try to register a database

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 89 Votes: 0 Revisions: 8

Symptom
You get a Failed to Register SQL Instance (failed to authenticate monitoring user) error when you try to register a SQL Server database.

Cause
SolarWinds DPA uses xp_logininfo to determine if the Windows user you provided as a database user during registration exists and whether it is an admin user. Unfortunately, if the account you provided cannot run xp_logininfo, DPA cannot continue with registering the database instance.

Workaround
There is a workaround you can use if the SQL Server allows both Windows and SQL server authentication.

 

  1. Use a SQL Server credential to register the database instance.
  2. After the database instance is registered, click Options > Update Connection Info to edit the database details.
  3. Select the database instance.
  4. Change the credentials of the database to the Windows user you originally wanted to use and then click Next.
  5. Click Update Connection Info.

The database instance should now be monitored using the Windows credential. 

Last modified
19:14, 22 Jun 2016

Tags

Classifications

Public