Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Database Performance Analyzer (DPA) > Error in setting up a DPA repository with Windows authentication

Error in setting up a DPA repository with Windows authentication

Updated March 9, 2017

Overview

Trying to create a new DPA repository but getting an error with Windows authentication:

An unexpected error occurred from com.confio.ignite.common.parameters.dao.ParameterDaoImpl.getRepositoryParameterValue: Could not get JDBC Connection; nested exception is java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

Environment

All DPA versions

Cause 

The Windows authentication may have an issue where DPA needs to try NTLMv2 to connect with the repository. For connections to monitored instance DPA trys connecting over Kerberos and then if there is a fail adds useNTLMv2 to the connection string and trys the connection again. 
The wizard does not add this for the connections to the repository. This is environmental to the Windows domain  

See the Understanding Kerberos and NTLM authentication in SQL Server Connections (© 2017 Microsoft, available at https://blogs.msdn.microsoft.com, obtained on July 6, 2017.) article for more information.

Resolution

  1. Go to the repo.properties file and open it in a text editor as an admin.
    For Windows the default path to this file is either:
    C:\Program Files (x86)\Confio\Ignite PI\iwc\tomcat\ignite_config\idc\repo.properties, or 
    C:\Program Files\Solarwinds\DPA\iwc\tomcat\ignite_config\idc\repo.properties

    For Linux or Unix: {DPA home}/iwc/tomcat/ignite_config/idc/repo.properties 
  2. Add the following line repo.jdbcDriverProperties=useNTLMv2\=true.
  3. Restart the "Ignite PI server" service in the services window for Windows or run shutdown.sh and startup.sh on Linux or Unix.
 
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.

 

Last modified
09:56, 6 Jul 2017

Tags

Classifications

Public