Business & Finance • Oct 07, 2026

QuickBooks Error 6189, 816: Expert Fix for Multi-User File Lock Failures

By Steven Moody

5 Views

QuickBooks Error 6189, 816 appears when QuickBooks Desktop cannot access a company file because of a multi-user access, hosting, database-service, or file-lock problem. The message commonly states that an error occurred when QuickBooks tried to access the company file, followed by (-6189, -816).

The error can be especially disruptive when several employees need the same company file for invoicing, payroll, reconciliation, or month-end accounting.

The good news is that Error 6189, 816 does not automatically mean that your company file is damaged or that your financial data is lost. In many situations, the problem is related to how QuickBooks is accessing the file rather than the accounting information stored inside it.

This guide explains what Error 6189, 816 means, what commonly triggers it, how to troubleshoot it safely, and how to prevent recurring multi-user access problems.

What Is QuickBooks Error 6189, 816?

QuickBooks Error 6189, 816 is a company-file access error associated with QuickBooks Desktop multi-user environments.

It can occur when QuickBooks Desktop detects that the company file is unavailable for the type of access being requested. For example, another QuickBooks session may still have the file open exclusively, the hosting configuration may be incorrect, or the database service may not be communicating correctly with the workstation.

A typical message is:

“An error occurred when QuickBooks tried to access the company file (-6189, -816).”

The important point is that several different conditions can produce company-file access failures. Therefore, you should identify the underlying condition instead of assuming that every 6189, 816 error requires the same fix.

Quick overview

Item

Details

Error

QuickBooks Error 6189, 816

Category

Company-file access / multi-user issue

Common environment

QuickBooks Desktop

Main symptom

Company file will not open correctly

Possible causes

Hosting, database service, network, file location, or locked session

Immediate concern

Users cannot access the company file

Data risk

The error itself does not prove that accounting data is damaged

Best starting point

Close QuickBooks sessions and verify the server/hosting setup

Why Does QuickBooks Error 6189, 816 Happen?

There isn't one universal cause. The error can appear when QuickBooks cannot establish the expected connection between the company file, database service, and user workstation.

1. Another user has exclusive access

If somebody opened the company file in Single-User Mode, other users may be prevented from accessing it through the normal multi-user workflow.

This is one of the first things to check before changing files or running repair utilities.

Ask every user to close QuickBooks completely. If one person still has the file open, have that user exit QuickBooks before testing again.

2. Hosting is configured incorrectly

In a multi-user setup, the computer hosting the company file needs the appropriate QuickBooks database service and hosting configuration.

If hosting is enabled incorrectly on a workstation, or the expected hosting configuration has changed, QuickBooks may have difficulty opening the company file across the network.

3. QuickBooks Database Server Manager isn't working correctly

The database service is responsible for helping QuickBooks Desktop users access company files stored on the host computer.

A stopped, incorrectly configured, or unavailable database service can produce errors that look like company-file problems even though the underlying file may be healthy.

4. Network communication is interrupted

A network interruption, incorrect firewall configuration, unstable connection, or inaccessible shared folder can prevent a workstation from communicating properly with the company-file host.

This is particularly relevant when:

  • The server can open the file but workstations cannot.

  • Only some users experience the error.

  • The problem began after a network or Windows change.

  • Multi-user mode suddenly stopped working.

5. Company file is stored in an unsuitable location

QuickBooks Desktop company files should be hosted in an environment designed for QuickBooks multi-user access.

Problems can occur when users attempt to work directly from:

  • Cloud-synchronization folders

  • Unsupported network storage arrangements

  • Removable media

  • Locations with unreliable connectivity

Moving a company file should be done carefully, with a verified backup available first.

6. An unexpected shutdown interrupted a QuickBooks session

Power failures, forced restarts, crashes, or network interruptions can leave the QuickBooks environment in an inconsistent state.

However, do not automatically assume that a .TLG file is the cause of Error 6189, 816. The transaction log should not be treated as the first explanation for every 6189 problem.

How to Fix QuickBooks Error 6189, 816

Work through the following solutions in order. Start with the least invasive checks before changing company-file-related files.

Solution 1: Close QuickBooks on Every Computer

First determine whether another user still has the company file open.

  1. Save work and close QuickBooks Desktop on every workstation.

  2. Close QuickBooks on the computer hosting the company file.

  3. Check that no employee is still using the company file.

  4. Wait briefly for all QuickBooks sessions to close.

  5. Reopen QuickBooks on the host computer.

  6. Test the company file.

  7. Then reconnect the workstations one at a time.

If the file opens normally after all sessions have been closed, the original problem may have been an active or lingering session rather than damaged accounting data.

Solution 2: Restart the Hosting Computer

If closing QuickBooks does not clear the problem, restart the computer that hosts the company file.

  1. Make sure all users have exited QuickBooks.

  2. Restart the host/server computer.

  3. Allow Windows to finish starting.

  4. Verify that the QuickBooks database service is running.

  5. Open the company file from the host.

  6. Test multi-user access from a workstation.

Restarting the host can clear temporary service or session problems without modifying the company file.

Why start with the host?

In a multi-user environment, the host is the central point through which the workstations access the company file. Troubleshooting individual workstations first can waste time if the underlying problem is actually on the server.

Solution 3: Verify QuickBooks Hosting Settings

Check the computer that stores and hosts the company file.

Open QuickBooks Desktop and review the File > Utilities options.

The exact wording can vary by QuickBooks Desktop version, but the important objective is to ensure that the computer intended to host the company file is configured for hosting and that workstations are not incorrectly configured as additional hosts.

If hosting is configured inconsistently, correct the configuration and restart QuickBooks before testing again.

Solution 4: Check QuickBooks Database Server Manager

The QuickBooks Database Server Manager should be available on the computer hosting the company file.

Check the service and company-file folder configuration.

A typical troubleshooting process is:

  1. Close QuickBooks Desktop.

  2. Open the QuickBooks Database Server Manager on the host.

  3. Confirm that the company-file folder is included in the scanned locations.

  4. Scan the folder if appropriate.

  5. Confirm that the database service is running.

  6. Reopen QuickBooks Desktop.

  7. Test the company file from the host and then from a workstation.

If the host itself cannot access the file, focus on the host, database service, and company-file path before troubleshooting individual workstations.

Solution 5: Check the Network Connection

If the file opens on the server but not on workstations, investigate network communication.

Check:

  • Whether the server is reachable from the workstation

  • Whether the shared company-file folder is accessible

  • Whether Windows network discovery/sharing settings have changed

  • Whether firewall settings are interfering with QuickBooks communication

  • Whether the issue affects all workstations or only one

A useful diagnostic test

If every workstation receives the error, investigate the host, database service, and network configuration.

If only one workstation receives the error while others work normally, investigate that workstation first.

This distinction can significantly reduce troubleshooting time.

Solution 6: Run QuickBooks Tool Hub

QuickBooks Tool Hub can be useful when the underlying issue involves QuickBooks program components or network configuration.

Use it as a troubleshooting utility rather than assuming it will automatically repair every 6189, 816 condition.

Depending on the problem, relevant areas can include:

  • Program Problems

  • Network Issues

  • QuickBooks Database Server Manager

After completing a repair or diagnostic operation, restart QuickBooks and test the company file again.

Solution 7: Check the .ND File

The .ND file is a configuration file that helps QuickBooks Desktop identify how a company file is accessed across a network.

If the .ND file is damaged or contains outdated information, multi-user access can be affected.

With QuickBooks closed:

  1. Open the folder containing the company file.

  2. Locate the corresponding .ND file.

  3. Create a backup before making changes.

  4. Rename the .ND file rather than immediately deleting it.

  5. Reopen QuickBooks.

  6. Allow QuickBooks to recreate the necessary network configuration information.

  7. Test multi-user access.

Do not rename random files simply because they have a similar name. Confirm that you are working with the .ND file associated with the correct company file.

Solution 8: Be Careful With .TLG Files

You may see recommendations online telling you to immediately rename the .TLG file for Error 6189, 816.

That approach should be used cautiously.

A .TLG file is associated with QuickBooks transaction logging and should not be treated as disposable troubleshooting material.

Before renaming any company-file-related file:

  • Make a verified backup.

  • Confirm that QuickBooks is closed everywhere.

  • Make sure you understand which company file you are working with.

  • Do not perform file manipulation during an active multi-user session.

If the company file exhibits broader signs of corruption or data integrity problems, use an appropriate backup/recovery or professional diagnostic process rather than repeatedly renaming files.

Solution 9: Move the Company File Only When the Storage Location Is the Problem

If the company file is stored in an unsuitable location, correcting the file path can resolve recurring access problems.

Before moving it:

  1. Close QuickBooks on every computer.

  2. Create and verify a backup.

  3. Copy the company file to the intended local/network location.

  4. Confirm that the new location is accessible to authorized users.

  5. Configure the QuickBooks hosting environment for the new folder.

  6. Test the file from the host.

  7. Test each workstation.

Do not simply drag the live company file between folders while employees are working in it.

Quick Diagnostic Decision Tree

A simple way to narrow down Error 6189, 816 is to ask these questions:

Can the server open the company file?

Yes:
The problem may involve workstation connectivity, network configuration, permissions, or multi-user communication.

No:
Investigate the company-file location, hosting configuration, database service, and file integrity on the host.

Can other workstations open the file?

Yes:
The problem is probably isolated to the affected workstation or its network connection.

No:
Investigate the server and shared network environment first.

Did the problem begin after a crash or forced shutdown?

Yes:
Check for incomplete QuickBooks sessions and network/service problems before modifying company-file-related files.

Did the problem begin after a QuickBooks upgrade?

Yes:
Verify that the appropriate database server components and hosting configuration correspond to the installed QuickBooks Desktop environment.

QuickBooks Error 6189, 816 vs. Related Errors

Understanding related error codes prevents you from applying the wrong solution.

Error

General problem area

6189, 816

Company-file access / multi-user environment

6190

Company-file access or mismatch condition

6175

Database service/hosting communication

6000-series errors

Various company-file access, network, or file-location conditions

H202

Multi-user hosting/network communication

6000-83

Company-file access/network-related condition

The numbers alone are not enough to diagnose the problem. The exact error message, number of affected users, company-file location, and hosting configuration all matter.

Real-World Troubleshooting Example

Consider a small accounting team using QuickBooks Desktop Enterprise on a shared company file.

One morning, every workstation receives Error 6189, 816, while the host computer can still open the file.

Instead of immediately modifying the company file, the administrator checks the environment.

The team discovers that the problem started after the server restarted unexpectedly overnight.

The troubleshooting sequence is:

  1. All QuickBooks sessions are closed.

  2. The host is restarted normally.

  3. The database service is verified.

  4. The company-file folder is checked.

  5. The host opens the file successfully.

  6. One workstation is tested.

  7. Additional workstations reconnect successfully.

In this scenario, the problem was related to the hosting environment rather than evidence of accounting-data loss.

The lesson: diagnose the environment before making changes to the company file itself.

How to Prevent QuickBooks Error 6189, 816

Preventing recurring multi-user problems requires consistent administration.

Use a dedicated hosting computer

Keep the company file on the intended host rather than allowing employees to create inconsistent copies across multiple machines.

Close QuickBooks properly

Avoid forced shutdowns whenever possible, particularly while users are actively entering transactions.

Maintain reliable backups

Regular, verified backups provide an important recovery option if a genuine file-integrity problem occurs.

Keep QuickBooks environments consistent

After upgrading QuickBooks Desktop, verify the corresponding database-server and hosting configuration.

Monitor network stability

A reliable local network is essential for multi-user QuickBooks Desktop environments.

Avoid unsupported file-storage practices

Do not treat cloud-synchronization folders, removable drives, or arbitrary file-sharing services as interchangeable with a properly configured QuickBooks multi-user environment.

Frequently Asked Questions

What does QuickBooks Error 6189, 816 mean?

It indicates that QuickBooks Desktop is having trouble accessing the company file, commonly in a multi-user environment. The underlying problem can involve hosting, database services, network communication, or a conflicting QuickBooks session.

Does Error 6189, 816 mean my company file is corrupted?

Not necessarily. The error itself does not establish that the company file is corrupted. First investigate active sessions, hosting, database services, network communication, and file location.

Can restarting the server fix Error 6189, 816?

It can resolve temporary hosting or database-service conditions. Close QuickBooks for all users before restarting the host and then test the company file from the server before reconnecting workstations.

Why does 6189, 816 happen only on one computer?

If other users can open the same company file successfully, the problem may be specific to that workstation, its network connection, or its QuickBooks configuration.

Can QuickBooks Tool Hub help with Error 6189?

It can help troubleshoot related programs and network conditions. However, Tool Hub should not be considered a universal solution for every cause of Error 6189, 816.

Should I delete the .TLG file?

Do not delete company-file-related files casually. Create a verified backup first and understand why a file is being changed. Renaming or manipulating a .TLG file should be considered only when appropriate to the diagnosed condition.

What should I do if Error 6189 keeps returning?

Recurring errors deserve deeper investigation. Check the hosting configuration, database service, network reliability, company-file location, QuickBooks versions, and whether users are improperly opening the file in different modes.

Is Error 6189 the same as Error 6175?

No. They can occur in related QuickBooks Desktop environments, but they point toward different troubleshooting areas. Error 6175 is more directly associated with the QuickBooks database service or hosting communication.

When should I stop troubleshooting myself?

If the error continues after basic hosting and network checks, affects multiple users, or is accompanied by other company-file errors, unexplained transaction behavior, or backup problems, stop making repeated file changes and obtain qualified technical assistance.

Final Takeaway

QuickBooks Error 6189, 816 is primarily an access problem that needs diagnosis—not a reason to immediately assume that your accounting data is lost.

Start with the safest checks: close QuickBooks for everyone, restart the hosting computer, verify the QuickBooks database service, confirm hosting configuration, and test the network connection. If the issue is isolated to one workstation, troubleshoot that workstation instead of modifying the company file.

Avoid jumping directly to .TLG, .ND, or other company-file changes without a backup and a clear reason. A structured diagnosis is safer and usually more efficient than trying multiple unrelated fixes.

If your business is blocked by recurring QuickBooks Error 6189, 816, Data Service Team can help identify the underlying multi-user, hosting, network, or company-file access problem.

Need expert assistance? Call Data Service Team at +1-(888)-718-7888 for QuickBooks Desktop troubleshooting and multi-user file-access support.