QuickBooks Error -6189, 82 -- Company File Locked in Single-User Mode

QuickBooks error -6189, 82 blocks access when the company file is held in single-user mode; our guide explains the causes and how to restore multi-user access.

When QuickBooks Desktop refuses to open your company file and reports error -6189, 82, the file itself is usually fine. Something else has it locked. Our engineers treat this as one of the more recoverable 6000 series errors, because in most cases the fix is a configuration change rather than a data repair.

What the error message says

The full message typically reads:

"QuickBooks is unable to open this company file. An error occurred when QuickBooks tried to access the company file. Error -6189, 82."

Some installations show a shorter variant: "Error -6189, 82: QuickBooks has encountered a problem and needs to close." Either way, the file does not open, or it opens read-only before failing.

What the code means

The -6189 family points to a mismatch between how the file is being opened and how it is currently locked. The , 82 suffix narrows it further: the database manager sees the file held in single-user mode, or in a state left over from a session that did not close cleanly. QuickBooks cannot reconcile the requested access mode with the lock on the file, so it stops.

A related code, -6189, 77, involves similar locking issues but usually points to permission problems on the hosting server. If you see 82 specifically, mode conflicts and stale locks are the first things to check.

What triggers it

The most common triggers, in rough order of frequency we see:

1. Another user has the file open in single-user mode, and a second workstation then tries to open it.
2. A previous QuickBooks session crashed or was force-closed, leaving a stale lock on the file.
3. The file is hosted on a computer where the QuickBooks Database Manager service is stopped or running under wrong credentials.
4. Hosting mode is enabled on a workstation that should not be hosting, so two machines fight over the lock.
5. Third-party software, such as a sync tool or backup agent, holds the file open while QuickBooks tries to start.

How to fix it

Scenario 1: another user holds the file in single-user mode.

1. Ask everyone to close the company file.
2. Have the user in single-user mode switch to multi-user mode from the File menu, or close the file entirely.
3. Reopen the file from your workstation.

Scenario 2: a crashed session left a stale lock.

1. Restart the computer that hosts the file, then restart the workstations.
2. Reopen the company file. If the error persists, rename the transaction log file, the one with the .TLG extension next to the company file, by adding OLD to its name. Do not delete it; keep it until the file opens and verifies cleanly.

Scenario 3: the Database Manager service is the problem.

1. On the hosting computer, open the Windows Services list.
2. Stop and then start the QuickBooksDBXX service, where XX matches your QuickBooks version year.
3. Open QuickBooks Database Server Manager, scan the folder holding the company file, and confirm the file appears in the scan results.

Scenario 4: hosting is enabled on the wrong machine.

1. On each workstation, press F2 in QuickBooks to open the Product Information window.
2. Check the Hosting line under Local Server Information. It should read "Hosting: Off" on every machine except the server.
3. If a workstation shows hosting on, turn it off from the File menu under Utilities, then restart that machine.

Scenario 5: third-party software holds the file.

1. Temporarily disable sync tools, backup agents, and antivirus file scanning for the folder holding the company file.
2. Reopen the file. If it opens, re-enable each tool one at a time to find the one causing the conflict.
3. Configure that tool to exclude the company file folder from real-time access.

If none of these resolves it, the file may have deeper damage, and our engineers can review a diagnostic before any repair is attempted.

How to prevent it recurring

Keep hosting enabled on exactly one computer, the server, and off everywhere else. Train users to close QuickBooks at the end of the day rather than leaving sessions open. Make sure the server is shut down properly, since hard shutdowns are a common source of stale locks. Finally, run the Database Server Manager scan after any QuickBooks update or server change, so the database manager always knows where the file lives.