After a recent QuickBooks Desktop update, our multi-user setup started throwing "Abort" / "Connection has been lost" errors every 5–30 minutes per workstation.

The root cause turned out to be a corrupt Entitlement Data Store (EntitlementDataStore.ecml) after the update. Intuit's License Service was failing to parse the EWS response using the cached entitlement file.

Fix: Rename the .ecml file, reopen QuickBooks, and let it re-register.

Time to fix: ~15 minutes per machine
Data risk: None

Environment

• QuickBooks Desktop Enterprise Solutions: Contractor 24.0 R21P (64-bit)
• Windows Server hosting company file via QuickBooks Database Server Manager (DB34)
• 3 workstations in multi-user mode
• Started immediately after a user initiated the auto-update
• Once one machine updated, the rest were forced to update to match
• Aborts started shortly afterward

Symptoms

• Users randomly kicked from the company file with:
  • "Abort"
  • "Connection has been lost"
• Happened on all workstations and the server
• Not tied to specific actions (saving invoices, reports, etc.)
• Appeared time-based rather than action-based
• DBMgr stayed running
• Hosting mode was correct
• No .ND / .TLG issues
• No antivirus interference

What We Ruled Out First

So you don't waste time chasing the wrong things:

• Version mismatch — all machines on 24.0 R21P ✓
• Hosting mode enabled on a workstation ✓
• Stale .ND file ✓
• Excessive .TLG growth ✓
• Firewall / Defender exclusions ✓

Root Cause

The actual clue was found in Event Viewer → Windows Logs → Application.

Filter on source: QuickBooks

Error:

An unexpected error has occurred in "Intuit QuickBooks Enterprise Solutions:
Contractor 24.0": LTSM:: Failure in parsing EWS Response. PSID=XXXXXXXXX

What That Means

• LTSM = License / Long-Term Subscription Module
• EWS = Intuit Entitlement Web Service

The R21P update appears to have changed something in the entitlement response. The cached EntitlementDataStore.ecml could no longer be parsed correctly.

Every 5–30 minutes QuickBooks performs an entitlement validation. When that validation failed, QuickBooks aborted the session. In a multi-user environment, this surfaced as users being kicked out of the company file.

Fix

Perform this on the server and every workstation.

Step 1: Close QuickBooks Completely

Make sure QuickBooks is closed on all machines.

Step 2: Rename the Entitlement File

Run PowerShell as Administrator:

# Rename the entitlement file instead of deleting it
$ecml = "C:\ProgramData\Intuit\Entitlement Client\v8\EntitlementDataStore.ecml"

if (Test-Path $ecml) {
    $stamp = Get-Date -Format 'yyyyMMdd-HHmmss'
    Rename-Item `
        -Path $ecml `
        -NewName "EntitlementDataStore.ecml.bak_$stamp"
}

Step 3: Reopen QuickBooks

1. Launch QuickBooks.
2. It should automatically recreate the entitlement file and revalidate the license.
3. Go to:Help → Manage My License → Sync License Data Online
4. Close QuickBooks.
5. Reopen QuickBooks.
6. Open the company file in multi-user mode.

Recommended Order

1. Server
2. Workstation #1
3. Workstation #2
4. Workstation #3

The .bak_<timestamp> rename provides an easy rollback if needed.

Verification

After 15–20 minutes of normal usage, run this on the server:

Get-WinEvent -FilterHashtable @{
    LogName='Application'
    StartTime=(Get-Date).AddMinutes(-20)
} -ErrorAction SilentlyContinue |
Where-Object {
    $_.ProviderName -like "*QuickBooks*" -and
    $_.Message -like "*LTSM*"
} |
Measure-Object |
Select-Object Count

Expected result:

Count : 0

If the count remains zero and users are no longer getting kicked, the issue is resolved.

Optional: Watch the Entitlement Log Live

Get-Content `
"C:\ProgramData\Intuit\Entitlement Client\v8\IntuitEntitlementLog.txt" `
-Tail 20 -Wait

Healthy output looks like:

INFO ... OfferingEntitlement get_State,
Return Status=Enabled,
Return Reason=EnabledTimeAvailable

If you continue seeing:

Failure in parsing EWS Response

then QuickBooks may still be using a cached state. Close QuickBooks, repeat the rename process, and relaunch.

Notes

• This is a per-machine fix.
• Fixing only the server will not solve the problem.
• Every workstation maintains its own entitlement cache.
• Users can continue working from fixed machines while others are repaired.
• No .QBW, .ND, or .TLG files are modified.
• This appears to be a licensing cache issue only.
• Pro and Premier 2024 users may be affected as well since they use the same entitlement client.

Hopefully this saves someone a few hours of chasing Database Server Manager, hosting mode, Tool Hub repairs, and networking issues.