QuickBooks Error -6000, -82 -- Multi-User Host Access Failure

Error -6000, -82 blocks multi-user access to a company file on the host; our engineers walk through hosting and transaction log repair to restore connectivity.

QuickBooks Error -6000, -82 is one of the most common 6000-series errors our engineers encounter in multi-user environments. It occurs when a workstation attempts to open a company file stored on another machine and QuickBooks cannot read the transaction log or establish a proper connection to the host. The result is a hard stop — no user can open the file until the underlying configuration or file damage is resolved.

What the Error Message Says

The full message typically 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: (-6000, -82)."

Some variations append additional context, such as the path to the company file or a note that the file may be in use by another program.

What the Code Means

The -6000 prefix indicates a company file access problem in the 6000-series family. The -82 sub-code specifically points to a failure reading the transaction log file (the .tlg file that sits alongside your .qbw company file). QuickBooks uses this log for database integrity and multi-user coordination. When the log is damaged, locked by another process, or the hosting configuration prevents proper communication between machines, QuickBooks refuses to open the file to protect against data corruption.

What Triggers It

Our engineers see this error most frequently in these scenarios:

1. Hosting is enabled on a workstation instead of only on the server. QuickBooks allows only one machine to host multi-user access. When hosting is turned on at multiple workstations, the database manager conflicts with itself.

2. The QuickBooks Database Server Manager is not running or has not scanned the folder containing the company file. Without a proper scan, the server manager does not know the file exists for sharing.

3. The .tlg transaction log file is damaged or has fallen out of sync with the company file. This can happen after an improper shutdown, a network drop during a save, or storage drive errors.

4. Folder permissions are insufficient. The Windows user account running the QuickBooks database service lacks full control over the folder where the company file resides.

5. A firewall or antivirus application is blocking QuickBooks components from communicating across the network.

How to Fix It

Our engineers recommend working through these scenarios in order of frequency.

Scenario 1: Hosting Is Enabled on Multiple Machines

1. On every workstation, open QuickBooks and go to File > Utilities.
2. If you see Stop Hosting Multi-User Access, click it. That means hosting is currently on and needs to be turned off.
3. If you see Host Multi-User Access, leave it — hosting is already off on that machine.
4. On the server machine only, go to File > Utilities > Host Multi-User Access and enable it.
5. Restart all machines and test opening the file from a workstation.

Scenario 2: The Database Server Manager Has Not Scanned the Folder

1. On the server, open QuickBooks Database Server Manager (installed alongside QuickBooks Desktop).
2. Go to the Folders tab and click Add Folder.
3. Browse to the folder containing your .qbw file and click OK.
4. Click Start Scan and wait for it to complete.
5. Verify the company file appears in the scan results with a green checkmark.
6. Attempt to open the file from a workstation.

Scenario 3: The Transaction Log Is Damaged

1. On the server, locate the company file folder.
2. Find the .tlg file with the same name as your company file (for example, CompanyFile.qbw.tlg).
3. Right-click the .tlg file and rename it to CompanyFile.qbw.tlg.OLD.
4. Do not delete it — keep it as a backup in case Intuit Data Services needs it later.
5. Open the company file directly on the server. QuickBooks will rebuild a fresh transaction log automatically.
6. Switch to single-user mode, then back to multi-user mode, and test from a workstation.

Scenario 4: Folder Permissions Are Insufficient

1. On the server, right-click the folder containing the company file and select Properties > Security.
2. Click Edit and then Add.
3. Type Everyone and click OK.
4. Check the box for Full Control under the Allow column.
5. Click Apply and OK, then test access from a workstation.

Scenario 5: Firewall or Antivirus Interference

1. Temporarily disable the workstation firewall and antivirus.
2. Attempt to open the company file.
3. If the file opens, re-enable the firewall and add QuickBooks executable paths (QBW32.exe, QBWDatabaseServerManager.exe, and FileManagement.exe) to the firewall exception list.
4. Re-enable antivirus and add the same executables to its exclusion list.

How to Prevent It Recurring

Our engineers recommend keeping hosting enabled on exactly one machine — the server — and verifying this after every QuickBooks update, since updates occasionally reset hosting settings. Run the Database Server Manager scan any time you move the company file to a new folder or install a new QuickBooks version. Ensure all workstations run the same QuickBooks release and update level as the server. Schedule regular verified backups using QuickBooks' built-in backup tool, which creates a clean copy without relying on the potentially damaged transaction log. Finally, confirm that Windows updates on the server do not reset folder permissions or firewall rules, as we see this reset trigger the error after patch cycles.