QuickBooks Error 6000, -107: How to Fix Server Folder Permission Errors

September 22, 2026 7 min read

QuickBooks Error 6000, -107 occurs when QuickBooks Desktop tries to open, create, or modify a company file (.QBW) hosted on a network server or shared directory, but the operating system blocks access due to insufficient Windows folder permissions or service account restrictions. This error indicates that the background database service (QBDataServiceUserXX) or the logged-in Windows user lacks Read, Write, and Modify privileges for the folder containing the company file. Granting full Windows sharing and NTFS security permissions to the QuickBooks data service user and network groups directly resolves the error.

Fast-Fix: The 45-Second Solution

To resolve Error 6000, -107 immediately, grant Full Control permissions to QBDataServiceUserXX and Everyone on the server folder hosting your company file. On your server, right-click the company file folder and select Properties. Go to the Security tab, click Edit, add the QBDataServiceUserXX account (matching your QuickBooks version year) and Everyone, and check the box for Full Control. Click Apply, switch to the Sharing tab, click Advanced Sharing > Permissions, grant Full Control to Everyone, and click OK.

Quick Status & Triage Snapshot

  • Data Risk Tier: Low (Your accounting database is intact; Error 6000, -107 is an operating system access-control failure, not internal file damage).
  • Multi-User Impact: High (All workstations connecting across the local network are blocked from opening the hosted company file).
  • Common Trigger: Moving the company file to a new server directory, Windows Server permission updates, or installing a new QuickBooks version without updating the dedicated database service user account.
  • Estimated Fix Time: 5 to 15 minutes.

Diagnostic Flowchart: Error 6000, -107 Decision Path

Plaintext

[Start: QuickBooks displays Error 6000, -107 when opening file]
       │
       ▼
Is the company file (.QBW) located on a local C: drive or a network server?
       │
       ├─► Local Workstation Drive (C:)
       │     └─► Right-click folder > Properties > Security > Grant current Windows user Full Control.
       │
       └─► Network Server / Shared Host
             │
             ▼
Check Server Folder Permissions: Security (NTFS) and Sharing Tabs
             │
             ├─► Is QBDataServiceUserXX listed with "Full Control"?
             │     │
             │     ├─► NO ──► Add QBDataServiceUserXX & Authenticated Users > Grant Full Control.
             │     │
             │     └─► YES ──► Is the file path mapped as a drive letter or using a UNC path?
             │                   │
             │                   ├─► Mapped Drive (e.g., Z:\Data) ──► Open via UNC Path (\\ServerName\Share).
             │                   │
             │                   └─► UNC Path ──► Rescan directory with QuickBooks Database Server Manager.

Is Your Data at Risk?

Error 6000, -107 occurs before QuickBooks can mount the database file into active workstation memory. Because the transaction engine is blocked from modifying records:

  • Data Integrity: Your general ledger entries, customer balances, and transaction tables remain completely safe.
  • Safe Actions: You can safely close error prompts, restart database services, and modify Windows permission tables without risking data corruption.
  • Precaution: Avoid copying raw .QBW files across the network while database services are actively attempting to mount them. Always run file operations when all users are disconnected.

Technical Anatomy: Why Permission Errors Trigger Error -107

When QuickBooks opens a company file in multi-user mode, it initiates a coordinated handshake between two distinct operational components:

  1. The Workstation User Session: The accounting user running QBW32.exe connects to the shared folder over the Windows Server Message Block (SMB) file-sharing protocol.
  2. The Database Engine Service (QBDataServiceUserXX): The host server runs an embedded Sybase SQL engine managed by qbdbmgrn.exe. To manage file locks and write to transaction journals, the service account (such as QBDataServiceUser34 for QuickBooks 2024 or QBDataServiceUser36 for QuickBooks 2026) requires direct operating system read/write/delete permissions.
  3. The Permission Choke Point: Windows security evaluates two separate permission layers: Share Permissions and NTFS Security Permissions. If the user or service account has Full Control under Sharing but only “Read” access under Security, Windows rejects the file lock attempt, and QuickBooks returns Error 6000, -107.

Differential Diagnosis: Don’t Confuse This With…

  • QuickBooks Error 6000, -77: Triggered when the company file is placed in an unauthorized location, such as a mapped drive root or external storage drive, rather than an NTFS-shared folder.
  • QuickBooks Error 6000, -305: Triggered when the companion transaction log (.TLG) or network data (.ND) files are corrupted or desynchronized, rather than an OS permission block.
  • QuickBooks Error 6000, -82: Occurs when a workstation is mistakenly hosting multi-user access instead of the dedicated server.

Step-by-Step Repair Guide

Follow these steps on the host server or computer storing your company file.

Step 1: Configure Windows NTFS Security Permissions

The underlying storage partition must grant explicit modify permissions to the QuickBooks service accounts.

  1. On the server hosting the company file, open File Explorer and locate your company data folder (e.g., C:\QuickBooksData or D:\CompanyFiles).
  2. Right-click the folder and select Properties.
  3. Go to the Security tab and click Edit.
  4. Check if the following user accounts and groups are listed:
    • QBDataServiceUserXX (where XX is your QuickBooks version number, such as 36 for 2026)
    • Everyone
    • Authenticated Users
    • SYSTEM
    • Administrators
  5. If any of these accounts are missing, click Add, type the name into the object field, click Check Names, and select OK.
  6. Highlight each account individually and check the box for Full Control under the Allow column.
  7. Click Apply, then click Advanced at the bottom of the Security tab.
  8. Check the box labeled Replace all child object permission entries with inheritable permission entries from this object, then click OK and confirm the prompt.

Step 2: Configure Windows Share Permissions

Share permissions govern access over the local area network.

  1. In the same folder Properties window, switch to the Sharing tab.
  2. Click Advanced Sharing.
  3. Ensure the box for Share this folder is checked.
  4. Click the Permissions button.
  5. Highlight Everyone and check the box for Full Control under Allow. (If Everyone is not listed, click Add, type Everyone, click OK, and assign Full Control).
  6. Highlight QBDataServiceUserXX (if present) and grant Full Control.
  7. Click Apply, click OK, and then click Close.

Step 3: Rescan the Directory with QuickBooks Database Server Manager

Once permissions are updated, the database service must rebuild the companion .ND network pointer file.

  1. On the host server, click the Start menu and open QuickBooks Database Server Manager.
  2. Go to the Scan Folders tab.
  3. Click Add Folder and select the shared company file directory configured in Steps 1 and 2.
  4. Click Scan.
  5. Once the scan completes, verify that your company file appears in the lower pane with the status showing active database access.

Step 4: Open the Company File Using a UNC Path

Using mapped drive letters (like Z:\Data) can cause Windows authentication tokens to drop. Using a Universal Naming Convention (UNC) path ensures persistent permission verification.

  1. Open QuickBooks on the client workstation.
  2. On the No Company Open screen, select Open or Restore an Existing Company.
  3. Choose Open a company file (.QBW) and click Next.
  4. In the Look in field, do not select a mapped letter. Instead, type the full network UNC path to your server (e.g., \\ServerName\QuickBooksData\CompanyFileName.qbw).
  5. Select the file and click Open.

Hard Stop: When to Escalate to IT Support

If Error 6000, -107 persists after applying Full Control permissions to all user groups and rescanning the database directory, stop manual changes if you encounter:

  • Active Directory Group Policy Overrides: In enterprise domain environments, an automated Domain Group Policy (GPO) may refresh every 90 minutes and strip local permissions from QBDataServiceUserXX. A domain administrator must update group policies at the domain controller level.
  • Server Service Failures: If the QuickBooksDBXX service refuses to start or crashes upon granting permissions, the underlying service installation may be damaged.

Closing the Books

QuickBooks Error 6000, -107 is an administrative access restriction rather than damage to your accounting ledger. By aligning both Windows NTFS security permissions and network share permissions to include QBDataServiceUserXX and Everyone with Full Control, you provide the database engine with the read/write access it requires to host your company file reliably across the network.

How to Fix QuickBooks Error 6000, -80: Troubleshooting “An Error Occurred When Opening the File”

July 2, 2026

QuickBooks 6000 Series Data Problems: Common Errors & Fixes

July 2, 2026