QuickBooks Error -6189-77 -- Hosting Configuration Conflict

QuickBooks error -6189-77 blocks access to your company file due to incorrect hosting settings; our engineers walk you through resolving the conflict and restoring access.

When QuickBooks Desktop displays error code -6189-77, the application cannot open the company file because the hosting configuration across your workstations is in conflict. Our engineers have resolved this error across multi-user setups of every size, and the underlying cause is almost always traceable to one of a small number of configuration problems. The fix is systematic and does not require advanced technical knowledge.

What the Error Message Says

The full message displayed by QuickBooks is:

"QuickBooks is attempting to open this company file. Before you can open the company file from your computer you must first open the company file on the computer in which the company file is located. (-6189, -77)"

In some installations the message may also read:

"An error occurred when QuickBooks tried to access the company file. Error codes: (-6189, -77)"

What the Code Means

Error -6189-77 is a 6000-series file-access error. The two-part code indicates that QuickBooks successfully located the company file on the network but could not establish the database connection needed to read it. Specifically, the -77 sub-code signals that the QuickBooks database service manager encountered a mismatch between the hosting state of the machine storing the file and the machine trying to access it. The application aborts the connection attempt to prevent data corruption.

What Triggers It

The most common triggers, in order of frequency our engineers observe, are:

1. Incorrect hosting configuration on workstations — More than one computer on the network has hosting enabled. Only the machine physically storing the company file should have hosting turned on.
2. The server machine has hosting turned off — The computer storing the .QBW file has hosting disabled, so QuickBooks cannot serve the file to other workstations.
3. Damaged or stale .ND (Network Descriptor) files — These small configuration files tell QuickBooks where the database server is. If they are corrupted or point to an old location, the connection fails.
4. Firewall or antivirus blocking QuickBooks database services — Security software is preventing communication on the ports QuickBooks uses for multi-user access.
5. Multiple QuickBooks database services running — Several versions of QuickBooks Desktop installed on the same server can create competing database services.

How to Fix It

Scenario 1: Correct the Hosting Configuration (Most Common Fix)

1. On every computer that runs QuickBooks, open the application.
2. Go to File > Utilities.
3. Look at the hosting status displayed in the menu. You will see either Host Multi-User Access or Stop Hosting Multi-User Access.
4. On the computer that stores the company file (your server), you should see Stop Hosting Multi-User Access — this means hosting is currently ON, which is correct.
5. On every other workstation, you should see Host Multi-User Access — this means hosting is currently OFF, which is correct.
6. If any workstation shows Stop Hosting Multi-User Access, click it to stop hosting. Only the server should host.
7. Restart all computers after making changes.

Scenario 2: Rebuild the Network Descriptor (.ND) Files

1. On the server computer, close QuickBooks on all machines.
2. Navigate to the folder containing your company file.
3. Locate files ending in .ND that share the name of your company file.
4. Right-click each .ND file and rename it (for example, add .OLD to the end).
5. Open the QuickBooks Database Server Manager on the server (Start menu > QuickBooks > QuickBooks Database Server Manager).
6. Click Add Folder, browse to the folder containing your company file, and click Start Scan.
7. Once the scan completes, open QuickBooks on the server and open the company file.
8. Switch to multi-user mode, then test opening the file from a workstation.

Scenario 3: Resolve Competing Database Services

1. On the server, press Windows + R, type services.msc, and press Enter.
2. Scroll through the list and look for entries beginning with QuickBooksDB.
3. If you see multiple QuickBooks database services (for example, QuickBooksDB31 and QuickBooksDB33), only the one matching your installed version year should be running.
4. Right-click the older or unused service and select Properties.
5. Set the startup type to Disabled and click Stop if it is running.
6. Confirm the correct service for your version is set to Automatic and is currently running.

Scenario 4: Check Firewall and Antivirus Interference

1. Temporarily disable third-party antivirus and firewall software on the server.
2. Attempt to open the company file from a workstation.
3. If the file opens successfully, re-enable your security software and add QuickBooks executables and database services to the exclusion or allow list.
4. Ensure Windows Firewall on the server allows QuickBooks through on both private and public networks.

How to Prevent It Recurring

Our engineers recommend documenting which machine serves as your QuickBooks server and labeling it clearly. Only that machine should ever have hosting enabled. When installing QuickBooks updates or new versions, verify the hosting configuration immediately afterward, as updates can occasionally reset these settings. Run the QuickBooks Database Server Manager scan any time you move the company file to a new location or install a new version year of QuickBooks Desktop. If you add a new workstation to the network, confirm hosting is off on it before the first user attempts to open the company file.