Database Management

DPA keystore certificate not applied after restart

After loading an SSL certificate through DPA Keystore Management, the new certificate did not persist after a service restart or server reboot. DPA continued to show the previous or self-signed certificate instead of the newly configured certificate.

First published date

7/14/2026 4:30 PM

Last published date

8/13/2026 9:35 PM

Overview

When you load a custom SSL certificate via DPA Keystore Management, restarting the Ignite PI service or rebooting the server does not retain the new certificate. Instead, it continues to present the previous or self-signed certificate. The working resolution is to stop the DPA service, rename the central cache database file, restart DPA, and then verify that the new keystore certificate is applied.

Product section

Database Performance Analyzer

Cause

The issue appears to be related to a cached certificate or central cache data, causing DPA to continue using the prior certificate state after a restart. The recommended remediation is to clear the Central_cache.db file so DPA can rebuild the cache and re-evaluate the configured keystore certificate on startup.

Resolution

  1. Stop the DPA service (Ignite PI Server) from the Windows Services tool.

  2. Go to the following path:

    C:\Program Files\SolarWinds\DPA\iwc\tomcat\ignite_config\iwc\central\cache

  3. Rename Central_cache.db to Central_cache_backup.db.

  4. Start the DPA server.

  5. After DPA is fully up, verify whether the new keystore certificate is now applied.