QuickBooks Error -6189, -106 -- Company File Will Not Open in Multi-User Mode

QuickBooks Desktop error -6189, -106 blocks access to the company file, usually over a mode conflict or a mismatched transaction log. Here is what it means and how our engineers clear it.

When QuickBooks Desktop refuses to open your company file and reports error -6189, -106, the cause is almost always on the hosting side rather than in your data. The file itself is usually intact. Our engineers treat this as an access and environment problem first, and a data problem only after the access issues are ruled out.

What the error message says

The full message reads:

"QuickBooks is unable to open this company file. An error occurred when QuickBooks tried to access the company file. Error codes: (-6189, -106). Please try again. If the problem persists, contact Intuit Technical Support."

The file may open for one user and fail for another, or fail for everyone on the network at once.

What the code means

The -6189 portion signals that QuickBooks could not obtain the right level of access to the database. The -106 portion points to the transaction log file, the .TLG companion that sits beside your .QBW file. Together they indicate that the database manager and the log file are out of step with the company file, or that another process is holding the file in a mode that blocks your session.

What triggers it

Three situations account for most cases we see:

1. Another user has the file open in a different mode, typically single-user mode while you are trying to open it in multi-user mode, or the reverse.
2. The QuickBooks Database Server Manager on the host machine is stopped, misconfigured, or scanning the wrong folder, so the log file and company file no longer match.
3. The .TLG file has drifted out of sync, often after an improper shutdown, a power loss, or a backup that copied the .QBW without its log file.

How to fix it

Scenario 1: a mode conflict with another user

1. Ask everyone to close the company file and exit QuickBooks completely.
2. On the host computer, open the company file in single-user mode.
3. Switch to multi-user mode from the File menu, then close the file.
4. Have each user reopen the file in multi-user mode.

Scenario 2: the Database Server Manager is not serving the folder

1. On the host computer, open the Windows Services list and confirm the QuickBooksDBXX service is running. The XX varies by version year.
2. If it is stopped, start it and set it to run automatically.
3. Open the Database Server Manager, and scan the folder that holds the company file. The scan re-registers the file and rebuilds the link between the .QBW and its .TLG.
4. Try opening the file again from a workstation.

Scenario 3: a mismatched transaction log

1. Make a verified backup of the company file before touching anything else.
2. Close QuickBooks on every machine.
3. In the folder holding the company file, rename the .TLG file so it has the word OLD at the end of its name. Do not delete it; it may be needed for recovery.
4. Reopen the company file. QuickBooks builds a fresh log file on open.

If the file still will not open, run the built-in verify and rebuild utilities on a restored backup. A file that fails verify after these steps has deeper damage, and that is the point where a manual repair of the data file is the appropriate next step.

How to prevent it from coming back

Keep the Database Server Manager running on one designated host, and only one. Hosting the file from multiple machines by accident is a common source of mode conflicts. Always let QuickBooks close the file before shutting down any computer. When you back up manually, copy the whole set, the .QBW and its .TLG together, or restore from a .QBB backup rather than a raw file copy. Finally, rescan the company file folder in the Database Manager after any server change, Windows update, or folder move. Those few habits remove nearly every repeat occurrence of this error we handle.