QuickBooksDBXX Service Won't Start ("Started Then Stopped" / Error 1069)? Fix the Logon
On the server that hosts your company file, multi-user mode breaks and you find the QuickBooksDBXX service (XX = your version) won’t stay running. You’ll see one of:
“The QuickBooksDBXX service on Local Computer started and then stopped.” “Error 1069: The service did not start due to a logon failure.”
…and workstations throw H202 because they can’t reach the database.
What it means: that service runs as a Windows account QuickBooks created for itself — QBDataServiceUserXX (32 = 2022, 33 = 2023, 34 = 2024…). When the service can’t start with a logon failure, the account’s password is out of sync, the account got disabled, or it lost the “Log on as a service” right. So the fix is on the server, at the service’s logon — not the company file.
Fix 1: Repair the service’s Log On (the direct fix)
- On the server, press
Win + R→services.msc. - Find QuickBooksDBXX → right-click → Properties → Log On tab.
- It should log on as
.\QBDataServiceUserXX. Two reliable ways to clear the logon failure:- Re-enter the password: select This account, then re-type / clear the password fields and Apply. Windows re-syncs the stored credential. (You’ll often get “…has been granted the Log on as a service right.”)
- Or use Local System: select Local System account → Apply. On many setups the service starts fine under Local System.
- Back on the General tab, set Startup type: Automatic, then Start.
- Reboot and switch a workstation to multi-user mode.
Fix 2: Un-disable or reset the QBDataServiceUserXX account
If the account itself is the problem (Pro/Enterprise — Win + R → lusrmgr.msc → Users):
- If QBDataServiceUserXX shows a down-arrow / “Account is disabled”, right-click → Properties → uncheck Account is disabled → OK.
- To reset its password from an admin Command Prompt:
net user QBDataServiceUserXX *— then set the same password on the service’s Log On tab (Fix 1).
If the service starts manually but fails on reboot, set Recovery → First/Second failure: Restart the Service in its Properties so it self-heals.
Fix 3: Confirm “Log on as a service”
A service account must hold the Log on as a service right. Win + R → secpol.msc → Local Policies → User Rights Assignment → Log on as a service → make sure QBDataServiceUserXX is listed (add it if missing). Re-entering the password in Fix 1 usually grants this automatically.
Fix 4: Delete and recreate the account + service
If it still won’t start, let QuickBooks rebuild it cleanly: delete the QBDataServiceUserXX account (and the broken service), then re-provision it by repairing the install / running QuickBooks Database Server Manager → Scan Folders, and re-enable hosting. Full steps: Recreate QBDataServiceUserXX with Database Server Manager.
Turn hosting back on
Once the service is Running (Automatic):
- On the server: File → Utilities should show Stop Hosting Multi-User Access (meaning hosting is ON — leave it).
- On each workstation: File → Utilities — if it shows Stop Hosting, click it. Only the server should host.
- Then on a workstation: File → Switch to Multi-user Mode.
FAQ
Which XX / user is mine? The number follows the year: 2022 → 32, 2023 → 33, 2024 → 34. Each installed year has its own QuickBooksDBXX service and QBDataServiceUserXX account.
It starts, then stops a few seconds later. That’s the logon failure (Error 1069) even when the pop-up says “started and then stopped” — re-enter the Log On password or switch to Local System (Fix 1), and confirm the account isn’t disabled (Fix 2).
Don’t I just need to restart the service? If the credential is out of sync, restarting fails the same way. You have to fix the Log On (Fix 1) or recreate the account (Fix 4) — restarting alone won’t stick.
Sources: Intuit — The QuickBooksDBXX service on Local Computer started and then stopped, Microsoft Learn — Error 1069: the service did not start due to a logon failure