QuickBooks Error -6160 -- Company File Fails to Open in Multi-User Mode

QuickBooks error -6160 blocks multi-user access to your company file. Learn what causes it and the steps our engineers use to restore network file access.

When QuickBooks Desktop refuses to open a company file and reports error -6160, the cause is almost always environmental rather than damage inside the file itself. The program cannot reach the file across your network, or it cannot obtain the access it expects while another workstation holds the file. Our engineers treat this as one of the more recoverable codes in the 6000 series, because the fixes rarely touch your accounting data.

What does the error message say?

The message typically appears at the point you open the company file, either by browsing to it or from the previously opened files list. The wording is generally:

"Error -6160: QuickBooks is unable to open the company file. An error occurred when QuickBooks tried to access the company file."

Some installations add a request to retry, or a note that the file may be in use. The code itself is the useful part. It tells you the failure happened during the connection handshake, not during a transaction.

What does error -6160 mean?

The 6000 series covers failures that occur while QuickBooks establishes a connection to a company file. The -6160 variant points at the network layer or the file path. QuickBooks asked the operating system for the file, and the answer it received back was not one it could work with.

The file is usually intact. The problem sits between the workstation and the file: a broken share, a mismatched hosting configuration, a firewall interruption, or a path that no longer resolves.

What triggers it?

Our engineers see three triggers far more often than any others.

First, incorrect hosting configuration. Only the computer that physically stores the company file should have hosting turned on. When two machines both host, or none does, multi-user connections fail.

Second, network and path problems. A mapped drive that dropped after a restart, a long file path, special characters in the file or folder name, or a server share with restrictive permissions can all produce this code.

Third, firewall or antivirus interference. Security software can block the ports QuickBooks Database Manager uses, which stops the connection before it starts.

A damaged or outdated QuickBooks Database Manager service on the host is a fourth, less common trigger.

How do you fix it?

Work through these scenarios in order, starting with the most common.

Confirm the hosting configuration

1. On every computer that uses QuickBooks, press F2 to open the Product Information window.
2. Look at the Hosting information line. It must read "Local server only" on every machine except the one storing the file.
3. On the host machine, it must read "Hosting mode on".
4. If a workstation shows hosting on, open the File menu, choose Utilities, and select "Stop hosting multi-user access". Restart QuickBooks.
5. Open the file again and confirm the error is gone before moving on.

Repair the network path

1. On the host, browse to the folder holding the company file.
2. Right-click the folder, choose Properties, then Sharing, and confirm the folder is shared with the users who need access.
3. On the workstation, remap the drive rather than relying on an old mapping. Use the UNC path, for example the server name followed by the share name, instead of a drive letter if mappings keep dropping.
4. Check the file name. Keep it short, avoid spaces and special characters, and confirm the full path is not excessively long.
5. Copy the file path from the host, paste it into the workstation's File Explorer address bar, and confirm the file opens from there before trying QuickBooks again.

Check firewall and antivirus settings

1. Add QuickBooks and the QuickBooks Database Manager to the allowed programs list in your firewall.
2. If your security software manages network traffic itself, add an exception for the ports the Database Manager uses, or temporarily disable that layer to test whether it is the blocker.
3. Re-enable everything before resuming normal work.

Refresh the Database Manager

1. On the host, open QuickBooks Database Server Manager from the Start menu.
2. Remove the old scan entry, re-add the folder holding the company file, and run a full scan.
3. Restart the host and try the file from a workstation again.

How can you prevent it from coming back?

Keep hosting enabled on exactly one machine, the one storing the file. Check this after any new workstation is added, because a fresh install defaults to hosting off and people toggle it while troubleshooting. Store the company file on the host's local drive rather than an attached USB device or a synced cloud folder, both of which interfere with database access. Re-run the Database Server Manager scan whenever the file moves or a new company file is created. Finally, keep firewall exceptions in place across software updates, since some security suites clear their allow lists when upgraded.