QuickBooks Error 6000, -83 occurs when QuickBooks Desktop cannot access the company file due to a host configuration error, inadequate Windows shared folder permissions, or an invalid file path. It can appear when opening, backing up, or restoring a company file in both single-user and multi-user configurations. To resolve the error, you must verify that the hosting computer has granted full read/write access to QuickBooks system users, confirm that the file path contains no special characters or excessive folder depth, and verify that the QuickBooks Database Server Manager is running correctly.
Fast-Fix: The 45-Second Solution
To quickly isolate Error 6000, -83: copy the
.QBWcompany file from its network share directly to the localC:\Users\Public\Documents\Intuit\QuickBooks\Company Filesfolder on your workstation. Open QuickBooks and open the local file. If it opens successfully, the issue is not data corruption; you must grant Full Control permissions toEveryoneandQBDataServiceUserXXon the host server’s shared folder.
Quick Status & Triage Snapshot
- Data Risk Tier: Low to Moderate (The file structure is generally intact, but attempting repeated manual saves during setup failures can stall transaction logs).
- Multi-User Impact: Critical (Can prevent all workstations from reading the shared company file).
- Common Trigger: Moving company files to new servers, missing Windows shared folder/NTFS permissions, storing files on unsupported Network-Attached Storage (NAS), or using special characters in folder names.
- Estimated Fix Time: 15 to 30 minutes.
Diagnostic Flowchart: Error 6000, -83 Decision Path
[Error 6000, -83 Appears]
│
├── Does the error occur while creating a backup or restoring a file?
│ ├── YES ──> Path or permission issue: Save backup to root directory (C:\).
│ └── NO ──> Does the error occur when opening a network file?
│ │
│ ├── Copy .QBW to local workstation drive C:\ and test opening:
│ │ ├── FAILS LOCALLY ──> File name/structure issue: Check for special characters;
│ │ │ run QuickBooks File Doctor.
│ │ └── OPENS LOCALLY ──> Host setup issue: Proceed with server folder permissions.
│ │
│ └── Is the file hosted on Linux or a consumer NAS?
│ ├── YES ──> Review SMB/Samba permissions and QBDBSM daemon setup.
│ └── NO ──> Audit Windows NTFS permissions for QBDataServiceUser.
Technical Anatomy: Why Host Configuration Fails
When QuickBooks opens a company file over a local area network, the underlying Sybase database engine requires elevated operating system permissions. It relies on a specific local user account created during the installation of the QuickBooks Database Server Manager: QBDataServiceUserXX (where XX corresponds to the software version, such as 34 for 2024 or 36 for 2026).
Error 6000, -83 triggers when one of several setup barriers prevents the database engine from initializing:
- Permission Denied (NTFS vs. Share): Windows enforces two layers of security: Share Permissions and NTFS (Security) Permissions. If a user has “Full Control” on the network share, but the underlying NTFS folder permissions exclude
QBDataServiceUserXX, the database manager crashes when trying to open the file. - Invalid Path Notation: The Sybase database engine cannot parse directory paths containing non-standard ASCII characters (such as
@,#,$,%, or&) or paths exceeding the maximum Windows path limit of 260 characters. - Non-Windows Hosting Issues: Storing a company file on a Linux server without the proper QuickBooks Database Server Manager package, or hosting it on a consumer-grade NAS box that lacks a native Windows database engine, prevents the file lock from executing.
Step-by-Step Repair Guide
Execute the following procedures to systematically identify and correct the host configuration breakdown.
Step 1: Clean the File Name and Directory Path
Before adjusting operating system security settings, verify that the file naming convention conforms to database standards.
- Open File Explorer on the host computer and locate the company file.
- Inspect the file name and the names of all parent folders in the path.
- Ensure there are no special characters in the file name or folder names (e.g., change
Smith & Sons #1 Accounting.qbwtoSmith and Sons 1 Accounting.qbw). - Ensure the file path is not deeply nested. An ideal path is:
C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\YourCompany.qbw - Verify the file extension is strictly
.qbwand not a double extension like.qbw.qbwor.qbb.qbw.
Step 2: Configure Windows Shared Folder and NTFS Permissions
Incomplete folder permissions are the most common source of Error 6000, -83 on Windows servers and peer-to-peer hosts.
- On the host computer, navigate to the folder where the company file resides.
- Right-click the folder and select Properties.
- Go to the Sharing tab and click Advanced Sharing…:
- Ensure Share this folder is checked.
- Click Permissions.
- Add Everyone and QBDataServiceUserXX (match your version). Grant both Full Control, Change, and Read.
- Click Apply and OK.
- Switch to the Security (NTFS) tab in the Properties window:
- Click Edit….
- Verify the following user accounts are listed and have Full Control checked under “Allow”:
- SYSTEM
- Administrators
- Everyone
- QBDataServiceUserXX
- If any of these accounts are missing, click Add…, enter the account name, click Check Names, and assign Full Control.
- Click Apply, then OK, and close the Properties dialog.
For an exhaustive checklist of required Windows security policies across corporate domain environments, consult Multi-User Access: Verifying Folder Sharing & Network Permissions.
[Required Security Permissions Matrix]
Account Name Share Permission NTFS (Security) Permission
--------------------------------------------------------------------------
QBDataServiceUserXX Full Control Full Control
SYSTEM Full Control Full Control
Administrators Full Control Full Control
Everyone (or Users Group) Change / Read Modify / Read & Execute
Step 3: Rescan the Directory with QuickBooks Database Server Manager
Once permissions are granted, you must force the database manager to recognize the updated security descriptor.
- On the host machine, open the Windows Start menu and launch the QuickBooks Database Server Manager.
- Click the Scan Folders tab.
- Click Add Folder and select the parent folder containing your
.QBWfile. - Click Start Scan.
- When the scan concludes, the directory status in the bottom pane should display “QuickBooks company file found.”
If the scanner skips your company file or throws an alert during the scanning process, refer to our troubleshooting resource: Scanning Issues: Database Server Manager Not Finding Company Files.
Step 4: Recreate the Network Descriptor (.ND) and Transaction Log (.TLG)
A damaged .ND file will continue to fail even after folder permissions have been corrected.
- Open the folder containing the company file on the host machine.
- Locate the corresponding
.NDand.TLGfiles:CompanyFile.qbw.ndCompanyFile.qbw.tlg
- Right-click each file and rename them with an added extension:
CompanyFile.qbw.nd.OLDCompanyFile.qbw.tlg.OLD
- Re-open QuickBooks on the workstation. The program will automatically communicate with the database server manager to generate fresh support files.
If you prefer to perform this manual reset alongside a comprehensive file cleanup, follow Manual Fix: Renaming .ND and .TLG Files to Resolve 6000-Series Errors.
Step 5: Special Handling for Linux and NAS Systems
If your company file is stored on a Network-Attached Storage (NAS) device or a Linux distribution:
- Consumer NAS Boxes: Most consumer NAS appliances use proprietary Linux variants that cannot run the Windows QuickBooks Database Server Manager executable. QuickBooks Desktop cannot manage transaction locking on these devices, routinely triggering Error 6000, -83. Move your company file to a physical or virtual machine running a supported version of Windows.
- Linux Enterprise Servers: If running an enterprise Linux server, you must install the official QuickBooks Database Server Manager RPM package and ensure the
smb.conf(Samba) configuration grants proper read/write/execute rights to all connected client nodes.
Review our dedicated operating guide for non-Windows architectures in Linux Server Guide: Troubleshooting Error 6000 on Database Manager and understand storage limitations in NAS Warning: Why Hosting QuickBooks on a NAS Usually Fails for Speed.
Differential Diagnosis: Don’t Confuse This With…
- Error 6000, -80: Indicates that a single-user file is being opened by another workstation or that internal file corruption has broken database pointers. Error 6000, -83 is fundamentally an environmental and setup conflict.
- Error 6000, -77: Fired when the company file is located on an external drive or mapped drive with an incorrect drive letter assignment.
- Error 6123, 0: Typically triggered when restoring a backup over a network share or during an active server disconnect.
Hard Stop: When to Escalate
If you complete the following checks without success, do not continue altering operating system permissions:
- The file fails to open locally on C:\: If copying the
.QBWdirectly to a local workstation drive still generates Error 6000, -83, the database file itself has sustained severe internal corruption. - The file size reads 0 KB: This indicates hard drive write failure or catastrophic file truncation.
- Immediately stop running permissions scripts and restore your most recent verified
.QBBbackup.
Closing the Books
QuickBooks Error 6000, -83 is an infrastructure warning indicating that the database manager cannot safely read or write to the storage directory. In almost all instances, simplifying the file path, granting Full Control permissions to QBDataServiceUserXX, and rescanning the host folder using the Database Server Manager resolves the block and allows your team to get back to work.