QuickBooks Error 6189-0: Company File Opens in the Wrong Mode

Error 6189-0 blocks QuickBooks Desktop when the company file opens in the wrong database mode; this guide shows how to get the file open again.

Error 6189-0 appears the moment you try to open a company file. QuickBooks reaches the database that holds your data, asks for it in one mode, and is offered another. The file stays shut, and the code gives little away. Our engineers clear this error often, and most of the time the data itself is intact; the configuration around it is what broke.

The exact message QuickBooks shows

The dialog usually reads, in part:

-6189, 0

An error occurred when QuickBooks tried to access the company file.

Some releases add a line asking you to try again. The number pair matters more than the wording. Note whether your screen shows "6189, 0" or "6189-0"; both point to the same fault.

What does the 6189-0 code mean?

Every 6000-series code covers trouble reaching or opening a company file. The 6189 member of that family is narrower. It means the request reached the database engine, and the engine refused to open the file in the mode QuickBooks asked for.

QuickBooks Desktop stores each company file inside a small SQL database. That database can be opened directly, in single-user mode, or through the database server service, in multi-user mode. When the two sides disagree about which mode applies, the open request fails and this code appears. The trailing zero is a status flag that adds no detail of its own.

What triggers error 6189-0?

Hosting changes lead the list. Multi-user hosting belongs on one machine, normally the computer that stores the file. If hosting gets switched on at a second computer, the two machines present the file in conflicting modes, and the open request fails.

A damaged network data file comes next. Each company file has a small companion file with the .ND extension, sitting in the same folder. It tells QuickBooks which computer hosts the data and in which mode. A stale or corrupt companion sends that request to the wrong place.

The database service is the third trigger. The QuickBooks database service must be running on the host. If it has stopped, the mode negotiation never happens and the file will not open. Moving or copying a company file to a new folder or computer can also leave the old companion behind, which produces the same result.

How do you fix error 6189-0?

Work through the scenarios in order. The first one settles most cases.

Correct the hosting mode setting

1. Close the company file on every computer, then close QuickBooks.
2. On the computer that stores the company file, open QuickBooks and go to the File menu, then Utilities.
3. If the menu shows "Host Multi-User Access", hosting is off here, so select it. The machine that holds the file should host. If it shows "Stop Hosting Multi-User Access", hosting is already on; leave it.
4. Open QuickBooks on each workstation in turn. Under File, Utilities, select "Stop Hosting Multi-User Access" if it appears, and confirm the change. Only the host should carry hosting.
5. Reopen the file on the host first, then from the workstations.

Rebuild the network data file

1. Close QuickBooks on every computer.
2. On the host, find the file that shares your company file's name and carries the .ND extension.
3. Rename it by adding OLD to its name. Do not delete it. QuickBooks builds a fresh companion when it next scans.
4. Open the QuickBooks Database Server Manager on the host. On the Scan Folders tab, add the folder holding your company file and start the scan.
5. Confirm the scan lists your company file, then open it again.

Check the database service

1. On the host, open the Windows Services console.
2. Find the QuickBooksDB service for your version year; the year forms part of its name.
3. If it shows as stopped, start it. Open its properties and set startup to Automatic.
4. If it was already running, restart it once, then try the file again.

After a move or a copy

If the error began right after the company file moved to a new folder or computer, rescan the new location in Database Server Manager. Open the file locally on the host once before sharing it over the network.

If the code survives every scenario above, the company file itself may need repair rather than the setup around it.

How can you stop it coming back?

Keep hosting on exactly one machine, the one that stores the file. After any update, reinstall, or new workstation, check the Utilities menu on each computer and switch off stray hosting. Rescan the company folder whenever the file moves, and set the database service to Automatic so it survives a restart.

Open the file from the same network location each time. A changed location can leave the companion file describing a setup that no longer exists. If you plan a server swap or a new host, settle hosting and rescan before the first multi-user session, and the file will open the way it did before.