Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

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

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

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

Tags

Classifications

Public