QuickBooks Company File Error Guide · 6000 Series
How to Fix QuickBooks Error 6000, 308
QuickBooks displays: "QuickBooks is unable to open this company file" — Error -6000, -308 when attempting to open a company file, typically in a multi-user environment.
Error 6000, 308 is a multi-user hosting conflict error — in the vast majority of cases it is caused by more than one computer hosting the company file simultaneously. QuickBooks requires exactly one computer to act as the server/host. When multiple workstations have hosting enabled, QB cannot determine which one is authoritative and throws 6000, 308. At QuickFix Bookkeeping, the hosting check resolves this in over 70% of cases.
The QuickFix Bookkeeping Distinction — Check Hosting First
Error 6000, 308 is fundamentally different from 6000, 77 or 6000, 83 — it is almost always a configuration error, not file damage.
Error 6000, 308 — this page
Multiple hosts conflict or permission issue. File is usually intact. Fix: stop hosting on all workstations, leave only the server hosting. Typically resolves without data recovery.
Error 6000, 77
File access or network permission problem. Usually single-user or involves QB Database Server Manager. .ND file rename and folder permissions are the primary fix.
Error 6000, 83
Insufficient permissions or wrong hosting computer. Server must run QB Database Server Manager and the file must be in a shared folder with Full Control permissions.
How to check hosting status in 30 seconds: On every computer where QB is installed, open QB (without opening a company file). Go to File > Utilities. If the menu shows "Stop Hosting Multi-User Access" — that computer has hosting enabled. If it shows "Host Multi-User Access" — hosting is correctly off. Only the server/host computer should show "Stop Hosting." If any workstation shows "Stop Hosting," click it to turn hosting off on that machine. Repeat on every workstation. Then retry opening the company file.
What Causes QuickBooks Error 6000, 308?
Multiple Computers Hosting Simultaneously
Most common cause — over 70% of 6000, 308 cases — hosting is enabled on one or more workstations in addition to the server. QB cannot determine which host is authoritative. Check every computer: File > Utilities. Only the server should show "Stop Hosting Multi-User Access."
Insufficient Permissions on Company File Folder
The QB Database Service user (QBDataServiceUserXX) or the Windows user account does not have Full Control permissions on the folder containing the company file. Common after moving the file to a new location or after a Windows update resets permissions.
Damaged or Missing .ND File
The .ND (Network Data) file that tells QB which database server manages the company file is corrupted or missing. QB cannot connect to the right host and throws 6000, 308. Renaming the .ND file forces QB to recreate it with the correct server reference during the next Database Server Manager scan.
QB Database Server Manager Not Running
On the server computer, the QB Database Server Manager service (QuickBooksDBXX) may have stopped running — from a reboot, a Windows update, or a service crash. Without this service running on the server, workstations cannot access the company file. Restart the service via services.msc.
Company File Name with Special Characters or Spaces
Special characters, extra spaces, or a very long file path can prevent QB from correctly resolving the file location. The company file name should use only letters, numbers, hyphens, and underscores. Rename the file to remove any spaces, special characters, or parentheses from the file name.
Firewall Blocking QB Database Ports
The Windows Firewall or third-party security software is blocking the ports QB uses for multi-user communication (8019, 56728, 55378-55382). This prevents workstations from connecting to the database server even when hosting is correctly configured. Port exceptions must be added on both server and workstations.
How to Fix QuickBooks Error 6000, 308
Start with Method 1 — the hosting check resolves 6000, 308 in the majority of cases without any further steps.
METHOD 1
Stop Hosting on All Workstations — Leave Only the Server Hosting
Do this first — resolves most 6000, 308 cases
Go to every computer that has QuickBooks installed — server and all workstations. The server should be the only computer with hosting enabled.
1
On each workstation (non-server computers): open QB (do not open the company file). Go to File > Utilities. If the menu shows "Stop Hosting Multi-User Access" — click it and confirm. After clicking, the option should change to "Host Multi-User Access" — this confirms hosting is now off on this workstation.
2
On the server/host computer: File > Utilities. Confirm the menu shows "Stop Hosting Multi-User Access" — this means hosting is correctly enabled here. If it shows "Host Multi-User Access," click it to enable hosting on the server.
3
After confirming hosting is correct on all machines: close QB everywhere. Restart QB on the server and open the company file first. Then have workstation users open QB and connect to the company file. Error 6000, 308 should be resolved.
QuickFix tip: A common cause of the wrong hosting configuration is a QB Desktop update or reinstall on a workstation that re-enables hosting by default. After any QB update on a workstation, always check File > Utilities to confirm hosting is not re-enabled.
METHOD 2
Restart QB Database Server Manager Service on the Server
Hosting correct — DB service not running
If hosting is correctly configured but 6000, 308 persists, the QB Database Server service may have stopped on the server. This service enables workstations to access the company file.
1
On the server: Windows + R > type services.msc > Enter. Find QuickBooksDB[XX] (where XX is your QB version year, e.g., QuickBooksDB24 for QB 2024). Right-click > Properties. Set Startup type to Automatic. Click Start if not running. Click Apply > OK.
2
Also in Tool Hub: open on the server > Network Issues > QuickBooks Database Server Manager > Scan Folders. Add the company file folder if not listed. Click Scan. This re-registers the company file with the database server and regenerates the .ND file. Retry opening from a workstation after the scan completes.
METHOD 3
Rename .ND and .TLG Files + Run QuickBooks File Doctor
Hosting + DB service correct — .ND damaged
1
Close QB on all computers. Navigate to the company file folder. Find the .ND file (same name as the .QBW) > right-click > Rename > add .old. Also rename the .TLG file the same way. Run QB Database Server Manager scan on the server (Method 2, step 2) to regenerate a correct .ND file. Retry opening.
2
File Doctor: Tool Hub > Company File Issues > Run QuickBooks File Doctor. Select the company file > Check your file and network (top option) > Continue > enter admin password. Allow 10-15 minutes. File Doctor checks both the file and the network configuration and applies the appropriate repairs for 6000, 308.
METHOD 4
Set Correct Folder Permissions for QBDataServiceUserXX
All above correct — permission issue
1
On the server: right-click the company file folder > Properties > Security > Advanced. Look for QBDataServiceUserXX (e.g., QBDataServiceUser24 for QB 2024). Confirm it has Full Control. If not listed: Edit > Add > type QBDataServiceUserXX > Check Names > OK. Tick Full Control > Apply > OK.
2
Also verify the company file folder is properly shared: right-click the folder > Properties > Sharing tab > Advanced Sharing. Confirm the folder is shared and that Everyone or specific QB user groups have at least Change permission in the Share permissions. Full Control in Security tab and at least Change in Sharing are both required for multi-user access to work.
METHOD 5
Update QB, Add Firewall Exceptions, Check File Name
All configuration correct — remaining causes
1
Update QB: on the server, right-click QB > Run as Administrator > Help > Update QuickBooks Desktop > Reset Update > Get Updates. Restart and install. Error 6000, 308 can result from an outdated QB build that has a known bug in multi-user connection handling.
2
Firewall ports: on both server and all workstations, add inbound and outbound exceptions for QB database ports (8019, 56728, 55378-55382). Tool Hub > Network Issues > QB Database Server Manager > Firewall Port tab shows the exact ports for your QB version.
3
File name: check the company file name for spaces, special characters, or parentheses. Right-click the .QBW > Rename. The ideal file name: letters, numbers, hyphens, underscores only. If the path is very long (more than 180 characters total), move the file to a shorter path — QB has a path length limitation.
Quick Reference
| Your situation |
Root cause |
Start with |
| Error after adding a new workstation to multi-user setup |
New workstation has hosting enabled |
Method 1 — stop hosting on all workstations |
| Hosting correct, error appears after server reboot |
QB Database Server service stopped |
Method 2 — restart QuickBooksDB service |
| DB service running, workstations still cannot open file |
Damaged .ND or permissions |
Methods 3 + 4 — .ND rename, permissions |
| All configuration correct — error persists |
Outdated QB, firewall, or file name |
Method 5 — update QB, add port exceptions |
Frequently Asked Questions
Why does QB allow hosting to be enabled on workstations at all if it causes this error?
QB Desktop can operate in both single-user mode and multi-user mode. In a single-user setup, each computer acts as its own host — so hosting is expected to be enabled on each standalone machine. The configuration becomes a problem only in a multi-user network setup, where exactly one computer should host the shared company file. QB Desktop does not automatically detect network topology and cannot distinguish between a standalone machine and a workstation in a multi-user setup — so it allows hosting to be enabled everywhere. A QB Desktop update or reinstall on a workstation also re-enables hosting by default, making this a recurring cause of 6000, 308 in multi-user environments. Checking File > Utilities after every QB update on every workstation is the key preventive step.
Does Error 6000, 308 mean my company file data is corrupted or at risk?
Not usually. Error 6000, 308 is primarily a configuration and access error — QB cannot find or connect to the company file, but the file itself is typically intact. In the vast majority of cases, once hosting and permissions are correctly configured, the company file opens and all data is present and unaffected. The risk of data corruption comes from force-closing QB while it is actively writing to the file, not from the 6000, 308 error itself. However, it is always wise to verify data integrity (File > Utilities > Verify Data) after resolving any 6000-series error, as the conditions that caused the error may have involved an interrupted write operation.
Can I open the company file in single-user mode while the multi-user 6000, 308 issue is being fixed?
Yes, in most cases. If the server computer can open the company file directly (even if workstations cannot), you can continue working in single-user mode while the network configuration is corrected. On the server, open QB and the company file normally. If it opens on the server, your data is accessible — the problem is only with the multi-user network connection, not the file itself. Use this as a workaround to keep operations running while you fix the hosting, permissions, or firewall configuration that is causing 6000, 308 for workstation users.
Related QuickBooks Company File Errors
Multi-User Access Still Broken After All Steps?
Let QuickFix Bookkeeping Restore Your Multi-User Setup.
Certified Intuit ProAdvisors — QuickBooks Network Configuration Specialists
Persistent 6000, 308 after correct hosting, permissions, and port configuration usually points to a Windows networking issue or an unusual server configuration that requires ProAdvisor-level network diagnostics. We restore multi-user access and keep it stable going forward.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Multi-user access restored fast.
