Applications Systems

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

A Failed to Register SQL Instance (failed to authenticate monitoring user) error occurs when you try to register a SQL Server database. If the account you provided cannot run xp_logininfo, DPA cannot continue with registering the database instance. There is a workaround you can use if the SQL Server allows both Windows and SQL server authentication.

First published date

11/21/2018 11:17 PM

Last published date

5/10/2019 3:24 PM

Overview

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

Product section

Database Performance Analyzer

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.

WARNING (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.

Resolution

Workaround

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

Use a SQL Server credential to register the database instance.
After the database instance is registered, click Options > Update Connection Info to edit the database details.
Select the database instance.
Change the credentials of the database to the Windows user you originally wanted to use and then click Next.
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.

Disclaimer: Please note, any content posted here is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.