QuickBooks Error 6000, -82: How to Unblock Connection to Company File

August 1, 2026 7 min read

QuickBooks Error 6000, -82 indicates that QuickBooks Desktop cannot open your company file because the connection to the host computer or server is blocked. This error typically occurs in multi-user environments when one or more client workstations are incorrectly set to host multi-user access, or when network communication between the workstation and the QuickBooks Database Server Manager is severed. Turning off hosting on all client workstations and restarting the database service on the host computer directly resolves this connection block in most cases.

Fast-Fix: The 45-Second Solution

To resolve Error 6000, -82 immediately, turn off hosting on every workstation: Open QuickBooks on each user PC, go to File > Utilities, and click Stop Hosting Multi-User Access if it appears. Only the main server should host files. Next, reboot the host server and restart the QuickBooksDBXX service in Windows Services. If the error persists, rename the .ND and .TLG files in your company folder.

Quick Status & Triage Snapshot

  • Data Risk Tier: Low. The error is a network connection handshake failure, not internal file damage.
  • Multi-User Impact: High. Usually prevents secondary workstations from opening the company file; the host computer can often still access it in single-user mode.
  • Common Trigger: A workstation computer accidentally enabling hosting, an ungraceful server restart, or a network firewall blocking port communication.
  • Estimated Fix Time: 5 to 15 minutes.

Diagnostic Flowchart: Error 6000, -82 Decision Path

[Start: Error 6000, -82 Appears]
       |
       v
Can you open the company file directly on the host computer?
       |
      +---> NO: Open Services.msc on the host. Is QuickBooksDBXX running?
      |            |
      |           +---> NO: Start the service and set startup type to Automatic.
      |           +---> YES: Rename .ND and .TLG files, then rescan folder via QBDBSM.
      |
      +---> YES: The file and database service are healthy.
                   |
                   v
Check client workstations: Is "Host Multi-User Access" turned on?
       |
      +---> YES on any PC: Select "Stop Hosting Multi-User Access" on that workstation.
      |
      +---> NO (Workstations clear): Check network connectivity and Windows Defender Firewall.

Is Your Data at Risk?

Your accounting data is safe. Error 6000, -82 is an environmental access block rather than a database corruption event.

  • Safe to proceed: If this error appeared when logging in, opening QuickBooks, or switching to multi-user mode, your transactions and lists are intact. You do not need to restore a backup file.
  • Caution required: If the error appeared immediately after an unexpected power outage or network disconnect during a file rebuild or large data import, verify the file once connectivity is restored by navigating to File > Utilities > Verify Data.

Technical Anatomy: What This Error Means

When QuickBooks runs in multi-user mode, a client workstation uses its local application executable (QBW32.exe) to request a network handshake with the host computer [4]. The host relies on the QuickBooks Database Server Manager (QBDBMgrN.exe) to coordinate read and write requests to the company file (.QBW).

Error 6000, -82 occurs when this handshake fails because:

  1. Conflicting Hosts: A client workstation has hosting turned on. When two machines broadcast that they are hosting the same file, the network protocol crashes to prevent split-brain data write conflicts.
  2. Dropped Socket Connection: The hosting computer terminated the database connection service or failed to maintain the network port session required by the workstation.
  3. Corrupted Network Descriptor File: The .ND file contains an outdated IP address or computer name for the server, causing workstations to route requests to a dead endpoint.

Differential Diagnosis: Don’t Confuse This With…

  • QuickBooks Error 6000, -83: Error -83 is a general configuration error often caused by incorrect folder permissions, file path issues, or saving backups over a network, whereas -82 specifically stems from blocked network communication and improper hosting states.
  • QuickBooks Error H202: While both indicate network communication blocks in multi-user setups, H202 indicates that the workstation cannot reach the IP address or server port, whereas 6000, -82 occurs after the path has been resolved but the file-level connection handshake is blocked or refused.

Step-by-Step Repair Guide

Follow these steps in sequence. Test file access after completing each step.

Step 1: Turn Off Hosting on All Client Workstations

In a QuickBooks network, only the dedicated server or the designated primary computer should host the file.

  1. Open QuickBooks on a workstation reporting the error.
  2. Do not open the company file; stay on the No Company Open window.
  3. Go to the File menu and choose Utilities.
  4. If you see Stop Hosting Multi-User Access, click it and click Yes to confirm [9].
  5. If you see Host Multi-User Access, leave it alone; this workstation is already configured correctly.
  6. Repeat this check on every user workstation on your network.

For detailed workstation configurations, review Multi-User Fix: How to Turn Off Hosting on All QuickBooks Workstations.

Step 2: Restart QuickBooks Database Services on the Host

  1. Log into your host server or main computer as an administrator.
  2. Press Windows Key + R, type services.msc, and press Enter.
  3. Locate the QuickBooks database service corresponding to your installed version:
    • QuickBooks 2024: QuickBooksDB34
    • QuickBooks 2025: QuickBooksDB35
    • QuickBooks 2026: QuickBooksDB36
  4. Right-click the service and select Properties.
  5. Set the Startup type to Automatic.
  6. Switch to the Recovery tab and change First failure, Second failure, and Subsequent failures to Restart the Service.
  7. Click Apply, then OK.
  8. Right-click the service in the list and select Restart.

Step 3: Rename Damaged .ND and .TLG Files

Network Descriptor (.ND) and Transaction Log (.TLG) files allow QuickBooks to communicate with the company database. When corrupted, they block connections.

  1. On the host computer, navigate to the folder containing your company file (.QBW).
  2. Locate the files sharing your company name with the extensions .ND and .TLG (for example, CompanyFile.qbw.nd and CompanyFile.qbw.tlg) [10].
  3. Right-click the .ND file, select Rename, and change the extension to .ND.old .
  4. Right-click the .TLG file, select Rename, and change the extension to .TLG.old .
  5. Open the QuickBooks Database Server Manager from your Windows Start menu.
  6. Click the Scan Folders tab, browse to your company file directory, and click Start Scan. This regenerates a clean .ND file.

If you encounter issues during this process, refer to Manual Fix: Renaming .ND and .TLG Files to Resolve 6000 Errors.

Step 4: Run QuickBooks File Doctor

If the connection remains blocked, use the automated diagnostic tool to inspect network permissions and firewall rules.

  1. Download and install the latest QuickBooks Tool Hub on the host server and workstation.
  2. Launch the Tool Hub and select Company File Issues.
  3. Click Run QuickBooks File Doctor.
  4. Select your company file from the drop-down menu or browse to find it.
  5. Choose Check your file and network, then enter your QuickBooks Admin credentials.
  6. Allow the tool to repair port exceptions and folder permissions.

Hard Stop: When to Call an Expert

Cease automated troubleshooting and escalate to a database administrator or technical support under these conditions:

  • The QuickBooksDBXX service on the server stops immediately upon startup with Windows Event ID 1000 or error 1067.
  • Your company file extension displays as .QBW but the file size shows 0 KB.
  • Running QuickBooks Database Server Manager produces an unhandled crash or reports that the underlying database engine cannot read the file allocation table.

Closing the Books

Error 6000, -82 can disrupt office workflows, but it almost never indicates data loss. It is simply a traffic signal failure between your computers. By verifying that only the server hosts the file, refreshing the database services, and generating a clean network descriptor file, you will restore multi-user access cleanly and safely.

QuickBooks Error 6190, -816: Resolving Transaction Log & File Discrepancies

October 2, 2026

QuickBooks Error 6176: Troubleshooting Firewall Blocks on Company File Paths

October 1, 2026

QuickBooks Error 6189, 816: Fix “Company File is Already in Use”

October 1, 2026