Database Management

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

This article outlines potential resolutions if you are unable to sign in the DPA Web Client. It specifically refers to repository issues.

First published date

10/23/2018 6:47 AM

Last published date

1/30/2023 7:13 PM

Overview

This article outlines potential resolutions if you are unable to sign in the DPA Web Client. It specifically refers to repository issues.

Product section

Database Performance Analyzer

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 called "SQL Server Network Configuration" and expand it.
  3. Click "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:

  1. Go to the following location on your DPA App Server:

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

  2. Make sure that the section titled "repo.port" has no values assigned to it.
  3. If there are values assigned to it, go ahead and clear this out.
  4. Once you clear this value, save the repo.properties file.
  5. 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.