How to Fix QuickBooks Error 6189 816

- Error 6189 816 means QuickBooks cannot access the company file because it is locked, corrupted, or stored in a location without proper permissions
- The most common cause is a single-user mode conflict: another user or background service has the file locked
- Renaming the .ND and .TLG files forces QuickBooks to rebuild them, which resolves the majority of persistent cases
- The QuickBooks File Doctor (Tool Hub) is the fastest automated fix for damaged company files
- Never store your company file on a USB drive, removable disk, or cloud-synced folder (these locations consistently trigger this error)
- All fixes must be applied on the host computer where the company file is stored
QuickBooks Error 6189 816 is a company file access error that blocks you from opening your company file. It appears when another user or service has the file open in single-user mode, or when the network descriptor and transaction log files are damaged. This guide covers all fixes verified on QuickBooks Desktop 2022 through 2026 on Windows 10 and Windows 11. Most cases resolve within 15 minutes using the Tool Hub methods below.
A support agent can walk you through the fix step by step.
+1 (800) 446-8848What Is QuickBooks Error 6189 816?
QuickBooks Error 6189 816 belongs to the 6000-series of company file errors. These errors share a common theme: QuickBooks cannot open, read, or write to the company file (.qbw). The 6189 816 combination specifically signals a file access conflict, usually because the file is already in use by another user, process, or service.
When this error occurs, you typically see one of these messages:
"An error occurred when QuickBooks tried to access the company file (-6189, -816)."
"QuickBooks is unable to open this company file. It may have been opened by another user."
The error appears most often when switching from single-user to multi-user mode, after a system restart, or when opening a company file that was not properly closed during the last session.
Symptoms
You may be experiencing Error 6189 816 if:
- The error message appears immediately when trying to open the company file
- QuickBooks opens but hangs on the company file selection screen
- The file opens for one user but shows the error for everyone else
- The error appeared after a system restart or Windows update
- QuickBooks was not closed properly during the last session (power outage, forced shutdown)
- The company file is stored on a USB drive, external hard drive, or cloud-synced folder
Root Causes
1. Single-User Mode Conflict
The most common cause. If one user has the company file open in single-user mode, no other user or process can open it. Background QuickBooks services can also hold the file in single-user mode invisibly, preventing access even when no one appears to be using it.
2. Damaged .ND or .TLG Files
QuickBooks creates two support files alongside every company file:
- The .ND file (Network Descriptor) stores network configuration so workstations can find the company file
- The .TLG file (Transaction Log) tracks recent transactions for recovery purposes
If either file is corrupted or mismatched with the .QBW file, QuickBooks cannot verify file integrity and blocks access with Error 6189 816.
3. Incorrect File Storage Location
QuickBooks requires the company file to be stored on a local hard drive with full read/write access. Common problematic locations:
- USB drives or external hard drives
- Cloud-synced folders (Dropbox, OneDrive, Google Drive)
- Read-only network shares
- The QuickBooks program folder itself
4. Insufficient Folder Permissions
The Windows user account running QuickBooks (and the QBDataServiceUser account used by QuickBooks services) needs full control permissions on the folder containing the company file. If permissions are restricted, QuickBooks cannot lock the file for exclusive access.
5. Outdated QuickBooks Version
Running a version of QuickBooks Desktop that is not compatible with the current Windows version can trigger file access errors. Intuit releases compatibility patches in quarterly updates.
A support agent can walk you through the fix step by step.
+1 (800) 446-88486. Firewall or Antivirus Blocking File Access
Security software can flag QuickBooks file operations as suspicious and block read/write access to the .QBW file, causing the 6189 816 error even when the file and permissions are correct.
Before You Begin
- Confirm which computer is the host (the machine where the company file is stored)
- Make sure all users have closed QuickBooks on every machine before troubleshooting
- Back up your company file before making any changes. Copy the .QBW file to a separate drive
- Have administrator privileges on the host computer
- Note your QuickBooks Desktop version year (check via Help > About QuickBooks)
- This error applies to QuickBooks Desktop on Windows only. QuickBooks Online does not have local company files
Step-by-Step Fix
Work through these methods in order. Methods 1 and 2 resolve over 80% of cases.
Method 1: Close All QuickBooks Instances and Restart
The fastest fix for a single-user mode conflict is to close every QuickBooks instance completely, including background processes.
- Ask all users to close QuickBooks on their computers
- On the host computer, press Ctrl + Shift + Esc to open Task Manager
- Click the Processes tab and look for any processes named QBW32.exe, QBDBMgrN.exe, or QBCFMonitorService.exe
- Right-click each one and select End Task
- Wait 30 seconds, then reopen QuickBooks on the host computer
- Try to open the company file
If the file opens, switch to multi-user mode (File > Utilities > Host Multi-User Access) before other users log in.
Method 2: Run QuickBooks File Doctor (Tool Hub)
QuickBooks File Doctor is the official Intuit tool for diagnosing and repairing company file errors including 6189 816. It checks file integrity, repairs the .ND file, and fixes folder permissions in a single scan.
- Download QuickBooks Tool Hub from the official Intuit support page
- Run the installer and complete the installation
- Open QuickBooks Tool Hub from the desktop icon
- Click Company File Issues in the left panel
- Click Run QuickBooks File Doctor
- In the File Doctor window, use the dropdown to select your company file, or click Browse to locate it manually
- Select Check your file (middle option) and click Continue
- Enter your QuickBooks admin password and click Next
- The scan runs for 5 to 15 minutes depending on file size
- When complete, open QuickBooks and try to access the company file
File Doctor resolves most 6189 816 errors caused by damaged .ND files or permission issues.
Method 3: Rename the .ND and .TLG Files
Renaming these support files forces QuickBooks to recreate them from scratch. This is the recommended fix when File Doctor does not resolve the issue.
- On the host computer, navigate to the folder where your company file is stored (commonly `C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\`)
- Look for two files with the same name as your company file but with .ND and .TLG extensions. For example:
- `MyCompany.qbw.nd`
- `MyCompany.qbw.tlg`
- Right-click the .ND file and select Rename
- Add `.OLD` to the end of the filename: `MyCompany.qbw.nd.OLD`
- Repeat for the .TLG file: `MyCompany.qbw.tlg.OLD`
- Open QuickBooks. It will automatically recreate both files
- Try opening the company file
If you cannot see the .ND and .TLG files, go to File Explorer > View > Options > Change folder and search options > View tab and enable Show hidden files, folders, and drives.
Method 4: Move the Company File to the Default Location
If your company file is stored on a USB drive, external disk, or cloud folder, move it to the standard local path QuickBooks expects.
- Close QuickBooks on all computers
- Copy the company file (.QBW) to: `C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\`
- Open QuickBooks on the host computer
- Go to File > Open or Restore Company
- Select Open a company file and click Next
- Browse to the new location and open the file
- If using multi-user mode, run QuickBooks Database Server Manager (see Method 5) to rescan the new location
Method 5: Run QuickBooks Database Server Manager
If the company file is hosted on a server for multi-user access, the Database Server Manager must be rescanned after any file move or rename.
- Open QuickBooks Tool Hub
- Click Network Issues
- Click QuickBooks Database Server Manager
- Click Browse and navigate to the folder containing your company file
- Click Start Scan and wait for the scan to complete
- Click Close when finished
- Open QuickBooks on each workstation and test access
Method 6: Fix Folder Permissions
QuickBooks requires full control on the company file folder for both your Windows user account and the QBDataServiceUser account.
- On the host computer, right-click the folder containing your company file (e.g., `C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\`)
- Select Properties > Security tab
- Click Edit
- Check the list for QBDataServiceUserXX (XX = your QB version: QBDataServiceUser26 for 2026, QBDataServiceUser25 for 2025, QBDataServiceUser24 for 2024, QBDataServiceUser23 for 2023)
- If the account is not listed, click Add, type the account name, and click Check Names
- Select the account and check Full Control under Allow
- Click Apply, then OK
- Restart QuickBooks and try opening the company file
A support agent can walk you through the fix step by step.
+1 (800) 446-8848Method 7: Update QuickBooks to the Latest Release
- Open QuickBooks Desktop
- Go to Help > Update QuickBooks Desktop
- Click the Update Now tab
- Check Reset Update to clear previously downloaded files
- Click Get Updates and wait for the download to complete
- Restart QuickBooks when prompted and allow the update to install
- Try opening the company file after the update
Method 8: Disable Antivirus or Firewall Temporarily
If all other methods fail, test whether your security software is blocking file access.
- Temporarily disable your antivirus or Windows Defender Real-time Protection
- Try to open the company file
- If it opens, add QuickBooks as a permanent exception in your security software:
- Add exceptions for `QBW32.exe`, `QBDBMgrN.exe`, `QBCFMonitorService.exe`, and the company file folder
- Re-enable your antivirus after adding exceptions
Refer to the Intuit firewall configuration guide for the full list of QuickBooks executable files and ports to whitelist.
When to Call Support
Contact Intuit Support if:
- Error 6189 816 persists after completing all eight methods
- File Doctor reports the company file is damaged beyond repair
- You see data loss or missing transactions after the file opens
- The error is accompanied by 6000-series codes like -82 or -83, which indicate deeper file corruption
- Your company file has not been backed up recently and you are concerned about data integrity
Reach Intuit support through the QuickBooks Contact page or via Help > QuickBooks Desktop Help inside the software.
Prevention Tips
- Store the company file on a local hard drive on the host computer. The recommended path is `C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\`
- Never store the file on a USB drive, external disk, or cloud-sync folder. These locations are the single most common preventable cause of 6189 816
- Back up daily. Use File > Back Up Company > Create Local Backup on a schedule. A current backup lets you restore without data loss if the file becomes corrupted
- Close QuickBooks properly. Always use File > Exit rather than closing the window directly. An improper shutdown can corrupt the .TLG file
- Run File Doctor quarterly to catch .ND and permission issues before they cause errors
- Keep QuickBooks updated. Intuit releases compatibility patches that prevent file access conflicts on newer Windows builds
Expert Insight
In my work as a CPA reviewing QuickBooks setups for small businesses, Error 6189 816 comes up almost every time a client has moved their company file to a shared drive or USB stick for convenience. I understand why they do it: they want to work from home or share access, but QuickBooks Desktop simply was not designed for that. The fix is always the same: move the file back to the local drive, run File Doctor, and set up proper multi-user hosting if remote access is needed. I have seen accountants spend hours on this when a five-minute file move would have resolved it immediately.
Emily Carter
CPA & Fintech Content Specialist
6000-Series Error Comparison
Error 6189 816 is one of several 6000-series company file errors. Use this table to confirm you are troubleshooting the right code.
| Error Code | What It Means | Most Common Cause | First Fix |
|---|---|---|---|
| -6000, -77 | File is open on another computer | Single-user mode conflict or file locked by background service | Close all QB instances (Method 1) |
| -6000, -82 | File was not closed properly | Power outage, crash, or forced shutdown corrupted the file | Run File Doctor (Method 2) |
| -6000, -83 | Error copying the company file | Insufficient disk space or file path too long | Move file to default QB folder (Method 4) |
| -6000, -301 | Company file not found | File was moved, renamed, or deleted | Browse to correct file location |
| -6189, -816 | File access conflict or permission issue | Single-user lock, damaged .ND/.TLG, or wrong storage location | Close all instances, rename .ND and .TLG (Methods 1, 3) |
If your error code does not appear above, check the Intuit 6000-series error guide for the full list of variants.
Get Support
The fastest way to resolve a QuickBooks issue is to speak directly with a support agent. Below you'll find the verified QuickBooks customer service phone number, current support hours, average wait time, and the best time to call to avoid long holds.
- Phone Number
+1 (800) 446-8848
- Support Hours
Mon–Fri, 6am–6pm PT
- Avg Wait Time
~8 minutes min
- Best Time
Early morning weekdays (6am–8am PT)
Related Errors
How to Fix QuickBooks Error 80070057
How to Fix QuickBooks Error H202
How to Fix QuickBooks Freezing or Not Responding
How to Fix QuickBooks Unrecoverable Error
How to Fix QuickBooks Error 6123
How to Fix QuickBooks Script Error
How to Fix QuickBooks Error 3371
How to Fix QuickBooks Has Lost the Connection to the Company File
How to Fix QuickBooks Error 80029c4a
How to Fix QuickBooks Error H505
Common Problems
How to Change the Beginning Balance in QuickBooks
How to Unapply a Credit in QuickBooks
How to Void a Check in QuickBooks
How to Print 1099 Forms in QuickBooks
How to Record Credit Card Payments in QuickBooks
How to Add a Bank Account in QuickBooks
How to Enter Invoices in QuickBooks
How to Search Invoices in QuickBooks
How to Delete a Deposit in QuickBooks
How to Record a Returned Check in QuickBooks
QuickBooks Resources
Conclusion
QuickBooks Error 6189 816 is a company file access error that sounds alarming but resolves quickly in most cases. The root cause is almost always a file lock from another user or service, a damaged .ND or .TLG file, or a company file stored in an unsupported location. Start with Method 1 (close all instances) and Method 2 (File Doctor), which together fix 80% of cases. If the error returns, check where your company file is stored. Moving it off a USB drive or cloud folder permanently eliminates the most common cause of recurrence.
Sources & References
- Fix Error 6000 Series When Opening a Company File - Intuit QuickBooks Support
- QuickBooks Tool Hub Download and Installation - Intuit QuickBooks Support
- Firewall and Security Settings for QuickBooks Desktop - Intuit QuickBooks Support
- Use Auto Data Recovery to Recover Data - Intuit QuickBooks Support
Disclaimer: OnCallSolve is an independent support directory. We are not affiliated with, endorsed by, or sponsored by Intuit, QuickBooks, or any software company mentioned in this article. All product names, logos, and brands are property of their respective owners. This article is provided for informational purposes only.
Emily Carter is a Certified Public Accountant (CPA) and fintech content specialist who bridges the gap between complex accounting concepts and practical software guidance. With 11 years of experience in public accounting and financial consulting, she has worked with hundreds of small and mid-sized businesses to set up, optimize, and troubleshoot QuickBooks systems. Emily earned her CPA license in 2015 and holds a Master of Accountancy from the University of Illinois at Urbana-Champaign. She now focuses on creating in-depth guides for QuickBooks Online, multi-currency setups, advanced reporting, and reconciliation errors. Her work is trusted by CPAs, bookkeepers, and business owners nationwide. She is based in Atlanta, Georgia.
Sandra Hoffmann is a senior accounting systems consultant and former Intuit product manager with 15 years of experience building and reviewing QuickBooks-related content, software documentation, and user guides. During her six years at Intuit, Sandra worked directly on the QuickBooks Online product team, overseeing feature rollouts and help center documentation for North America. Since leaving Intuit in 2019, she has run her own consulting practice helping mid-market companies select, implement, and troubleshoot accounting software. Sandra is a Certified Management Accountant (CMA) and holds a B.S. in Finance from Purdue University. She is based in Indianapolis, Indiana. Sandra reviews OnCallSolve content with a focus on product accuracy, updated UI instructions, and alignment with current QuickBooks release notes.
Frequently Asked Questions
The error itself does not cause data loss. It simply blocks access. However, if QuickBooks was not closed properly before the error appeared (for example, after a crash), the .TLG transaction log file may contain unsaved transactions. Running File Doctor (Method 2) recovers these where possible. Always maintain a daily backup to protect against data loss in any scenario.
In multi-user mode, the QuickBooksDBXX service on the host must have the file open simultaneously for all users. If a workstation previously opened the file in single-user mode and did not release the lock, multi-user mode fails with this error. The fix is to close QuickBooks on all machines, end any QBW32.exe processes in Task Manager, then reopen from the host in multi-user mode using File > Utilities > Host Multi-User Access.
The .ND file tells QuickBooks where to find the company file on the network. If it contains an outdated server name or IP address, QuickBooks cannot locate the file even though it exists. The .TLG file can become mismatched if it was created by a different version of QuickBooks. Renaming both files forces QuickBooks to recreate them correctly when it next opens the company file.
Possibly. QuickBooks Desktop supports network access only through a proper multi-user setup using QuickBooks Database Server Manager on the host. Simply placing the file in a shared folder without running Database Server Manager will cause 6189 816 and similar errors. Run Method 5 (Database Server Manager scan) to configure network access correctly. Never use consumer cloud sync tools (OneDrive, Dropbox, Google Drive) for QuickBooks company files.
If File Doctor reports the file is damaged, use QuickBooks Auto Data Recovery to restore recent transactions. Go to the folder containing your company file and look for a subfolder named QuickBooksAutoDataRecovery. It contains a backup copy of the .QBW and .TLG files from the last session. Follow the Intuit Auto Data Recovery guide to restore. If no recovery files are present, restore from your most recent manual backup.
The account name maps to your QuickBooks version year: QBDataServiceUser26 (2026), QBDataServiceUser25 (2025), QBDataServiceUser24 (2024), QBDataServiceUser23 (2023), QBDataServiceUser22 (2022). Check your version via Help > About QuickBooks if you are unsure. Add the correct account with Full Control permissions on the company file folder as described in Method 6.
Windows updates occasionally reset firewall rules or modify file permission settings, both of which can trigger 6189 816. After a Windows update, run Method 7 (update QuickBooks to match the new Windows build), then run Method 5 (Database Server Manager scan) to refresh network permissions and .ND files. Also check that your antivirus did not add QuickBooks to a blocked-applications list during the update process.
Was this article helpful?