PerpetualBooks
Sunset TimelineKeep It RunningBy VersionError CodesHacksPlaybooksDownloads Start with the survival guide

QuickBooks Error -6000, -83 -- Network and Permission File Access Failures

Last reviewed 2026-07-02 4 min read

Error -6000, -83 blocks company file access across a network or during restore; our engineers walk through each trigger and the concrete steps to resolve it.

QuickBooks Error -6000, -83 is one of the most frequently encountered 6000-series errors. It surfaces when a user attempts to open, restore, or convert a company file and QuickBooks cannot complete the operation. The error can appear whether the file is stored locally or on a network share, and it has several distinct triggers — each with its own resolution path.

What the Error Message Says

The full message typically reads:

"QuickBooks is unable to open the company file. An error occurred when QuickBooks tried to access the company file. Error codes: (-6000, -83)."

In some scenarios the wording varies slightly — for example, during a restore from a .QBB backup, the message may reference the backup file path instead of the working .QBW file. The two codes always appear together.

What the Code Means

The -6000, -83 combination indicates that QuickBooks started the file-open handshake but was denied at a layer below the application itself. The -6000 prefix designates a file-access family error, while the -83 sub-code specifically signals that the connection was refused or broken — most commonly due to folder permissions, database server hosting configuration, or file-level damage within a backup.

What Triggers It

Our engineers have identified five primary trigger scenarios, listed here from most to least common:

  1. Multi-user hosting misconfiguration — QuickBooks Database Server Manager is not running or the folder is not properly scanned and shared.
  2. Insufficient Windows folder permissions — the user account opening the file lacks full control over the folder containing the .QBW file.
  3. Damaged or incomplete .QBB backup file — the backup was created on a version mismatch or was interrupted during creation.
  4. Firewall or antivirus blocking QuickBooks ports — security software is intercepting the database connection.
  5. File stored on a NAS device or non-Windows share — QuickBooks requires a Windows-hosted share for reliable multi-user access.

How to Fix It

Scenario 1: Multi-User Hosting Misconfiguration

  1. On the machine hosting the file, open QuickBooks Desktop and go to File > Utilities.
  2. If you see Stop Hosting Multi-User Access, the machine is already hosting — proceed to step 3. If you see Host Multi-User Access, select it and follow the prompts.
  3. Open QuickBooks Database Server Manager (installed alongside QuickBooks Desktop).
  4. Under the Folders tab, click Browse and select the folder containing the company file.
  5. Click Scan. Wait for the scan to complete and confirm the company file appears in the results list.
  6. On each workstation, ensure File > Utilities > Host Multi-User Access is not selected — only the server machine should host.

Scenario 2: Insufficient Windows Folder Permissions

  1. Right-click the folder containing the .QWB file and select Properties.
  2. Go to the Security tab and click Edit.
  3. Select the user group (or add the specific Windows user) and check Allow for Full Control.
  4. Click Apply, then OK.
  5. Repeat on the server machine if the file is stored on a network share — the share-level permissions must also grant full control.

Scenario 3: Damaged or Incomplete Backup File

  1. Attempt to restore the .QBB file on the same machine and QuickBooks version that created it.
  2. If the restore fails, try restoring from an earlier backup if one is available.
  3. If no valid backup exists, our engineers can attempt manual extraction of the .QBB contents and reconstruction of the company file. This requires the backup file and details about the QuickBooks version that created it.
  4. To prevent version-related restore failures, confirm the QuickBooks version and release on the source machine by pressing F2 and checking the Product Information screen before creating future backups.

Scenario 4: Firewall or Antivirus Blocking

  1. Temporarily disable the firewall and antivirus on both the server and workstation.
  2. Attempt to open the company file.
  3. If the file opens successfully, re-enable the firewall and add QuickBooks executable paths to the exception list: QBW32.exe, QBW32Premier.exe, QBW32Pro.exe, and FileManagement.exe.
  4. Ensure ports 8019, 10133, and 40308 through 40313 are open for inbound traffic.

Scenario 5: File Stored on a NAS Device

QuickBooks does not reliably support company files stored directly on Network Attached Storage devices or non-Windows shares. Move the .QBW file to a Windows machine, configure that machine as the host using Database Server Manager, and have workstations connect through the Windows share.

How to Prevent It Recurring

  • Designate a single Windows machine as the dedicated host and run Database Server Manager scans after any file relocation.
  • Apply full Windows folder permissions proactively to the company file folder for all QuickBooks users.
  • Maintain at least two generations of .QBB backups on separate storage media.
  • Keep all workstations and the server on the same QuickBooks version and release.
  • Avoid storing company files on NAS devices, USB drives, or cloud-synced folders such as OneDrive or Dropbox.
Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.

Start with the survival guide Browse error codes