Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > 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 Jamin Walters on May 23, 2018

Views: 1,190 Votes: 0 Revisions: 9

 

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.

 

This issue can usually be seen in the wizard.log file found in DPA home/iwc/tomcat/logs/wizard.log with an error like the following. 

 

WARN   (2018-05-17 16:12:23,781.MDT) [http-nio-8123-exec-7] SQLServerSetupDaoImpl - xp_logininfo failed to return login information: java.sql.SQLException: Could not obtain information about Windows NT group/user 'domain\user', error code 0x5.



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. 

 

If the above workaround is not an option then this command must work outside of DPA and find a root cause seems to be a SQL server issue. 

Try running the following in SQL server management studio connected to the monitored instance 

 

xp_logininfo 'domain\user', 'all' 

 

You may then check that

the user indeed exists in the Active Directory; in particular, are you sure it’s not a SQL Login for which somebody pre appended the domain name?
the SQL Server service account is not a disabled/locked account

If all above fails, you may want to add the service account running SQL Server into the built-in Active Directory Group called Windows Authorization Access Group and try the command again. 

 

 

Last modified

Tags

Classifications

Public
/*]]>*/