Embedded database has crashed and Capital, or Capital Manager Essentials cannot connect

2023-07-29T01:01:51.000-0400

Summary

This article provides instructions on how to restore the database after a database crash occurred


Details

Client connections fail with popup window: "Connection Failed - Could not connect to Capital Manager [Essentials]. Application terminated"

When an attempt is made to re-start the Manager service, it runs and then stops by itself. The Manager log file states that it can't connect to the database. 

The server crash has corrupted the postmaster.pid lock file. The postmaster.pid file gets created when the embedded database is started. It gets deleted when the database is stopped. When a server crashes the .pid file remains and it causes a problem.

To fix this problem:

  1. Ensure the Embedded Database Windows service is stopped
  2. Delete the file [Capital or Capital Essentials Home directory]\embeddeddata\data\postmaster.pid 
  3. Re-start all Capital Windows services

KB Article ID# MG604911

Contents

SummaryDetails

Associated Components