QuickBooks Error -6189, 83: Company File Opened in the Wrong Mode

Error -6189, 83 stops QuickBooks Desktop from opening a company file because of a mode mismatch. Learn what it means and how to clear it.

Error -6189, 83 stops QuickBooks Desktop from opening a company file because the open request conflicts with the mode the file is already in. In most cases the data itself is intact. The conflict sits between the workstation, the transaction log, and the network files that track the file across your network. Our engineers clear this one regularly, and the sections below work through it from message to fix.

The message you see

Most installs show a dialog that reads:

An error occurred when QuickBooks tried to access the company file. Please try again. If the problem persists, contact Intuit Technical Support and provide them with the following error codes: (-6189, 83).

Newer releases sometimes shorten the wording to a line stating QuickBooks is unable to open the company file, followed by the same pair of codes. The exact text varies by version. The two numbers at the end are what identify the fault.

What does -6189, 83 mean?

The first code places this in the 6000 family, which covers failures to reach or open a company file. The second number, 83, narrows the cause to a mode mismatch. A company file can be held in single-user mode or in multi-user mode. When QuickBooks asks for one and finds the file held in the other, the request is refused outright.

A transaction log or a network descriptor that is out of step can report the wrong mode even when nobody has the file open. That is why the error can appear first thing in the morning, on a machine nobody else is using.

What triggers it?

• The file is already open in single-user mode on another machine while you request multi-user mode, or the reverse. This is the trigger our engineers see most often.
• The transaction log (.tlg) no longer matches the company file (.qbw). A crash, a forced shutdown, or a backup restored beside an old log will do it.
• The .nd and .dsm files that describe the file on the network are stale, often after the file is moved or the hosting machine changes.
• The QuickBooks Database Server Manager is not running, or hosting is switched on at more than one machine.
• Rarely, the company file itself is damaged.

Fixing it, trigger by trigger

Work through the scenarios in order. Each one takes only a few minutes, and the first addresses the most common cause.

Clear the mode conflict

1. Ask everyone to close the company file and exit QuickBooks on every machine, including the one that stores the file.
2. Restart the machine that stores the file first, then the workstations.
3. Open the file on the storage machine before anyone else does, and set the mode you want from the File menu.
4. Let other users open the file once the host is in.

Retire a stale transaction log

1. Confirm QuickBooks is closed on every machine, then copy the .qbw file somewhere safe.
2. Open the folder that holds the company file and find the matching .tlg file.
3. Rename it by adding .OLD to the end. Do not delete it, since a renamed log can still support a recovery later.
4. Reopen the company file. QuickBooks builds a fresh log as it opens.

Rebuild the network files

1. Close QuickBooks on every machine.
2. In the same folder, rename the .nd and .dsm files that share the company file's name by adding .OLD to each.
3. Reopen the file on the hosting machine. New descriptor files are created automatically.

Reset hosting and the database server

1. On the machine that should host the file, open the Windows Start menu and launch the QuickBooks Database Server Manager.
2. On the Scan Folders tab, add the folder that contains the company file and run the scan.
3. On each workstation, open the File menu and then Utilities. An option to stop hosting multi-user access means hosting is on there by mistake; switch it off.
4. Reboot in order, host machine first.

If the file itself is damaged

1. Open the file as the admin user and run Verify Data, under Utilities on the File menu.
2. If verification reports damage, run Rebuild Data from the same menu and accept the backup prompt.
3. If the rebuild fails or the error returns, the damage is past what the built-in tools can repair.

Keeping it from coming back

Open the file on the host machine first after any restart, then let others join. Decide which machine hosts the file and leave that arrangement alone. Hosting on two machines at once invites exactly this error. Switch modes deliberately from the File menu rather than mid-task.

Restore backups to your Documents folder or Desktop, never beside an old .tlg file or into the QuickBooks program folder. After moving the company file or updating the software, run a Database Server Manager scan. Keep a regular backup schedule so a mismatched log can always be retired without risk.