Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Database Performance Analyzer (DPA) > DPA will not restart after crash due to improperly closing connection to the respository

DPA will not restart after crash due to improperly closing connection to the respository

Table of contents

Overview

DPA may crash and not properly close the connection to the repository database. You may see the following message because the new instance of DPA conflicts with the original instance:

The Ignite PI Server process was recently restarted after a hard shutdown. In this case, wait 1 - 2 minutes before attempting to navigate to the DPA web page.

Environment

  • All versions of DPA

Steps

1. Log in to the DPA repository database as the DPA user and run the following commands:

 

update conprm set v=’STOPPED’ where p=’IDC_STATUS’;
delete conprm where p=’IDC_WIZARD_URL’;


2. Restart DPA.

Last modified
19:13, 22 Jun 2016

Tags

Classifications

Public