Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Unable to connect to the DPA repository when signing in from the DPA console

Unable to connect to the DPA repository when signing in from the DPA console

Updated November 7, 2016

Overview

This article overviews potential resolutions if you are experiencing an inability to sign in the DPA Web Client and it is specifically referencing repository issues.

Environment

All DPA versions

Cause 

This can have multiple causes. However, one thing to check would be if you are using dynamic ports, and that DPA is also configured to connect to a dynamic port

Typically, dynamic ports are used when monitoring a named SQL instance

Resolution

  1. Verify that your server is using dynamic ports by navigating to the server in question, and opening SQL Configuration Manager.
  2. Go to the tab on the left indicating "SQL Server Network Configuration" and expand it.
  3. Click into the "Protocols for MSSQLSERVER", and then right-click the "TCP/IP" and select Properties.
  4. Click the "IP Addresses" tab, and scroll down to the bottom to see if there is anything set in the "TCP Dynamic Ports" section.

 

If you are using dynamic ports:
Go to the following location on your DPA App Server:

{DPA Install Directory}\DPA\iwc\tomcat\ingite_config\idc\repo.properties

  1. Make sure that the section titled "repo.port" has no values assigned to it.
  2. If there are values assigned to it, go ahead and clear this out.
  3. Once you clear this value, save the repo.properties file.
  4. Restart the Ignite PI Service in services.

 

Try to access the DPA console after trying the above steps to see if you are now able to access your repository.

 

Last modified

Tags

Classifications

Public