Fix Eaglesoft intermittent service crashes with TCP connection errors

draft · practice-management eaglesoftpattersondatabase-corruptionpractice-management

Generated by docuprocessor (prompt article/v3) · 2026-04-22 15:30

Source thread

thread_id: spaces/AAAA05BdS6s/threads/hPUbTy5ASK8 · 9 msgs · first 2025-01-31 · participants: Tech ATech B

Tech A 2025-01-31 19:00

For Tribeca Murray, they have been calling recently since their ES stops working sporadically, its working now, I can see this is the event that displays on the patterson server status, any ideas?

image/png image.png

The log entries dated **01/31/2025** show a sequence of service state changes for **Patterson Database Service, Patterson Application Service, and Patterson API Service**. At **1:03 PM**, an error message reads: *"The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error,"* followed immediately by the Application Service entering the **Stopped state**. By **1:13 PM**, all three services (Database, Application, and API) are logged as having returned to the **Running state**; a red arrow annotation points to this recovery sequence.

Tech B 2025-01-31 19:01

is there anything in the task scheduler for that time frame? Maybe there is a script that kills the DB in a brutal way?

Tech A 2025-01-31 19:02

No, the only thing in task scheduler is the usual script to stop / start the db for backups, it doesn't seem to happen every day, this is the last time it happened before today, same message

image/png image.png

**Visible Log Entries (dated 01/28/2025):** - **1:57 PM (×2):** "Could not connect to net.tcp://localhost:2010/ApplicationUpgradeStatusService. The connection attempt lasted for a time span of 00:00:04.0236417 / 00:00:04.0405877. TCP error code **10061**: No connection could be made because the target machine actively refused it **127.0.0.1:2010**." - An earlier entry references: "The server did not provide a meaningful reply; this may be caused by a contract mismatch, a premature session shutdown or an internal server error." - A 6:30 AM entry (partially visible) references the **Patterson Database Service** entering the **Running state**. **TCP Error 10061** is explicitly displayed twice, targeting **localhost port 2010** for the **ApplicationUpgradeStatusService**.

Tech B 2025-01-31 19:03

what is the size of the db files? I remember they were telling me once that the log file should not be large. If it is, then there is an issue

Tech A 2025-01-31 19:05

is it pattersonPM.db? if so, 3.5gb

Tech B 2025-01-31 19:06

there are 2 files

Tech B 2025-01-31 19:06

pattersonPM.db is the actual database there should be a send file pattersonPM.log

Tech A 2025-01-31 19:07

(no text)

image/png image.png

**Windows File Explorer** showing the directory path **D:\Eaglesoft\Data**, containing three files: - **sqla0001.tmp** — 165,064 KB, modified 01/31/2025 at 1:55 PM - **PattersonPM.db** — 3,599,880 KB (≈3.4 GB), modified 01/31/2025 at 1:13 PM - **PattersonPM.log** — 1,600 KB, modified 01/31/2025 at 1:13 PM (displayed in **orange/amber text**) The `.log` file size is highlighted in orange, which in Windows Explorer typically indicates a file flagged for attention based on display settings or a custom view configuration.

Tech B 2025-01-31 19:07

yeah, that one and the size is fine. I guess, time to call the support

---
title: "Fix Eaglesoft intermittent service crashes with TCP connection errors"
category: practice-management
tags: ["eaglesoft", "patterson", "database-corruption", "practice-management"]
source_thread_id: "spaces/AAAA05BdS6s/threads/hPUbTy5ASK8"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T15:30:06"
participants: ["Tech A", "Tech B"]
---

# Fix Eaglesoft intermittent service crashes with TCP connection errors

## Problem

Eaglesoft stops working sporadically at a client office. The Patterson server status logs show a pattern of service failures where the Patterson Database Service, Patterson Application Service, and Patterson API Service crash and then automatically restart within 10 minutes. The error sequence includes "The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error" followed by TCP error code 10061 when trying to connect to the ApplicationUpgradeStatusService on localhost:2010. The crashes appear intermittent, occurring every few days rather than daily.

## Resolution

1. Check the Patterson database file sizes in `D:\Eaglesoft\Data`:
   - Verify `PattersonPM.db` size (3.5GB is normal for this case)
   - Confirm `PattersonPM.log` file size is reasonable (1.6MB was acceptable in this case)

2. Review Task Scheduler for any scripts that might be forcefully stopping database services outside of normal backup routines

3. If database file sizes are normal and no conflicting scheduled tasks exist, escalate to Patterson support as the TCP connection errors to the ApplicationUpgradeStatusService suggest an internal service communication issue that requires vendor assistance

No definitive resolution was reached in this case - escalation to Patterson support was recommended.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/hPUbTy5ASK8`
- Attachments:
  - ![image.png](../attachments/hPUbTy5ASK8.hPUbTy5ASK8/image.png) — The log entries dated **01/31/2025** show a sequence of service state changes for **Patterson Database Service, Patterson Application Service, and Patterson API Service**. At **1:03 PM**, an error message reads: *"The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error,"* followed immediately by the Application Service entering the **Stopped state**. By **1:13 PM**, all three services (Database, Application, and API) are logged as having returned to the **Running state**; a red arrow annotation points to this recovery sequence.
  - ![image.png](../attachments/hPUbTy5ASK8.OrilG8VvS1s/image.png) — **Visible Log Entries (dated 01/28/2025):**

- **1:57 PM (×2):** "Could not connect to net.tcp://localhost:2010/ApplicationUpgradeStatusService. The connection attempt lasted for a time span of 00:00:04.0236417 / 00:00:04.0405877. TCP error code **10061**: No connection could be made because the target machine actively refused it **127.0.0.1:2010**."
- An earlier entry references: "The server did not provide a meaningful reply; this may be caused by a contract mismatch, a premature session shutdown or an internal server error."
- A 6:30 AM entry (partially visible) references the **Patterson Database Service** entering the **Running state**.

**TCP Error 10061** is explicitly displayed twice, targeting **localhost port 2010** for the **ApplicationUpgradeStatusService**.
  - ![image.png](../attachments/hPUbTy5ASK8.-mzBlDPHn34/image.png) — **Windows File Explorer** showing the directory path **D:\Eaglesoft\Data**, containing three files:

- **sqla0001.tmp** — 165,064 KB, modified 01/31/2025 at 1:55 PM
- **PattersonPM.db** — 3,599,880 KB (≈3.4 GB), modified 01/31/2025 at 1:13 PM
- **PattersonPM.log** — 1,600 KB, modified 01/31/2025 at 1:13 PM (displayed in **orange/amber text**)

The `.log` file size is highlighted in orange, which in Windows Explorer typically indicates a file flagged for attention based on display settings or a custom view configuration.

Generated article

draft