Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

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