Database Management

DPA Central reports invalid credentials or shows a registered server as unavailable

DPA Central lists a registered remote DPA server as unavailable or reports an authentication error because the DPA application credentials saved in Central do not match a valid account on the remote DPA server.

First published date

8/31/2026 3:25 PM

Last published date

8/31/2026 3:25 PM

Overview

A remote DPA server can be reachable from DPA Central while still failing authentication. Verify that the Central Server and remote server use the same valid local or AD/LDAP-backed DPA account, update the saved credentials in Central, and allow the next polling cycle to run. If the server remains unavailable after the credentials are corrected, refresh the DPA Central cache and review the Central and authentication logs.

A remote DPA server appears in the Unavailable DPA Servers section on the DPA Central page. DPA Central may display one of the following messages:

  • Invalid credentials provided for repository.

  • Unable to authenticate user using LDAP.

  • A related authentication error.

The server may still be reachable when tested from DPA Central, but Central cannot retrieve information from it.

Product section

Database Performance Analyzer

Resolution

1. Verify the account on the remote DPA server

Sign in directly to the affected remote DPA server with an administrator account.

For a local DPA user:

  1. Go to Options > Administration > Users & Contacts > User Administration.

  2. Locate the user configured for Central-to-server communication.

  3. Confirm that the account is enabled and is not locked or expired.

  4. Reset the password and save the change, if necessary.

For an Active Directory (AD) or LDAP account or group:

  1. Confirm that the account is not locked or expired in AD or LDAP.

  2. Confirm that AD or LDAP authentication is configured on the affected remote DPA server.

  3. Confirm that the same user or group is configured on the Central Server and the remote DPA server.

  4. Confirm that the account can authenticate directly to the remote DPA server.

2. Synchronize the credentials in DPA Central

In DPA Central:

  1. Go to Options > Administration > Display > Manage Central.

  2. Select the affected registered server.

  3. Update the saved username and password so they match the account accepted by the remote DPA server.

  4. Save the configuration.

For a local DPA user, use the same username and password on the Central Server and every connected remote DPA server. Read-only permissions are sufficient for viewing data from remote repositories.

3. Allow Central to retry the connection

Return to the Central page and allow the next polling cycle to run. You can also refresh the Central page after updating the credentials.

The affected server should move out of Unavailable DPA Servers after Central successfully authenticates and retrieves its data.

If the server remains unavailable

Refresh the Central cache after confirming that the credentials are correct:

  1. Log in to the server where DPA Central is running.

  2. Stop the DPA service.

  3. Navigate to:

    DPA-install-dir\iwc\tomcat\ignite_config\iwc\central

  4. Delete the cache and lucent-index folders.

  5. Start the DPA service.

  6. Open the Central page and verify the registered server status.

Coordinate the service restart with the environment owner because DPA Central is temporarily unavailable while the service is stopped.

If the issue continues, verify the following:

  • The Central Server and remote DPA server are running the same DPA version. DPA Central cannot display data from a remote server running a different version.

  • The registered server hostname, port, and protocol are correct.

  • The remote DPA server accepts the configured account when logging in directly.

  • The account was not locked by repeated failed authentication attempts.

  • The DPA Central log contains the same authentication error shown in the user interface.

For troubleshooting, review central.log in the DPA logs directory. This log contains messages associated with DPA Central. If AD or LDAP authentication is involved, also review auth.log for login and directory-integration errors.

Expected result

After the same valid DPA application credentials are configured on the Central Server and the affected remote DPA server, DPA Central authenticates successfully and displays the remote server and its monitored database information.

Related documentation