QuickBooks Company File Error · 6000 Series
How to Fix QuickBooks Error 6177, 0
QuickBooks displays: "We're sorry, but QuickBooks can't open your company file. Error Codes: (-6177, 0)"
Error 6177 is a path error — not a file damage error. At QuickFix Bookkeeping, the first question is always: did anything change about where the file is stored? A moved or renamed folder resolves in under 2 minutes. Your data is almost certainly intact.
The QuickFix Bookkeeping Distinction — Path Error vs Access Error vs Wrong Error
Most guides jump straight to File Doctor when the fix is usually just pointing QuickBooks to the correct location. Three different problems look identical on screen.
Path Error — most common
The file was moved, the folder renamed, the drive letter changed, or QB's memorised path no longer exists. Fix: open QB → File → Open or Restore Company → browse to the file's new location. Resolves in under 2 minutes.
Access Error — second most common
The path exists but QB can't reach it — network share disconnected, folder permissions wrong, or file is on an unsupported location (NAS, cloud sync). Fix: copy file to local C: drive, test from there, then fix the underlying access issue.
6177 vs 6000-83
6177 = QB can't reach the path at all. 6000-83 = QB reached the file but can't read it (file damage). Fix 6177 by fixing the path. Fix 6000-83 with File Doctor. Wrong diagnosis wastes time.
6177 vs 6175
6177 = path problem. 6175 = path is fine, but QBDBMgrN.exe (database service) is not running on the server. Fix the service for 6175, not the path.
6177 vs 6176
6177 = path stored in QB is wrong. 6176 = QB can't identify the server at the network level — DNS or IP address failure. Fix the QBDSM scan and .ND file for 6176.
Running File Doctor for a 6177 path error won't fix the underlying location problem. File Doctor diagnoses and repairs file and network access issues — but if QB simply has the wrong path memorised, File Doctor has nothing to fix. Always correct the path first (Method 1), then escalate if the error persists.
What Causes QuickBooks Error 6177, 0?
Company File Moved or Folder Renamed
Most common cause — the company file or its containing folder was moved, renamed, or reorganised after QuickBooks memorised its location. QB's shortcut still points to the old path, which no longer exists. Opening the file directly from its new location via File → Open or Restore resolves this in under 2 minutes.
Network Drive Letter or UNC Path Changed
The mapped network drive letter used to access the server changed (e.g. from Z: to Y:), or the server was renamed changing its UNC path. QB cannot navigate to the old path. Reconfiguring the mapping to a consistent drive letter or UNC path, and re-opening the company file from there, fixes this.
Stale or Corrupt .ND Network Descriptor File
The .ND file stores the network address QB uses to reach the company file on the server. If the server's name or IP changed and the .ND wasn't regenerated, QB follows the stale address and reports 6177. Deleting the .ND and running a QBDSM scan rebuilds it with the correct current address.
File on Unsupported Location
Files stored in cloud-synced folders (OneDrive, Dropbox, Google Drive) or on NAS/external drives produce 6177 because QB cannot maintain a stable path to these locations. Cloud sync tools rename, lock, and move files during sync cycles — QB cannot reliably navigate the path.
Folder Permission Change
Windows folder permissions on the company file directory were changed — common after a server OS reinstall, domain policy update, or group policy change. The QBDataServiceUser account or the logged-in user no longer has Read/Write access to the folder, producing 6177 as an access denial.
Hosting Misconfiguration
In a multi-user setup, a workstation is trying to open the company file directly rather than routing through the server running QBDSM. Or hosting was enabled on the wrong machine. The path is reachable but the access model is broken, producing 6177 in multi-user mode only.
How to Fix QuickBooks Error 6177, 0
Start with Method 1 — open the file directly from its current location. This resolves most 6177 cases in under 2 minutes.
METHOD 1
Open the File Directly from Its Current Location
Under 2 minutes — try this first
When QB shows 6177 from the Recent Files list or a desktop shortcut, it's trying to open from a memorised path that no longer exists. Opening the file directly from its current location bypasses the stale path and re-registers the correct location.
1
In QuickBooks: File → Open or Restore Company → Open a company file → Next. Browse to the folder where your .QBW file currently lives. If you're not sure where it is — search File Explorer for *.QBW to locate it.
2
Select the file → Open. QB re-memorises the correct path and opens the file. After it opens, press F2 and note the file path shown in the Product Information window — this confirms QB has registered the new location. If you're using a desktop shortcut to open QB, update or delete the shortcut — it may be pointing to the old path and will trigger 6177 again on the next launch.
METHOD 2
Copy to Local C: Drive + Create Portable Copy + Restore to Server
File on network, NAS, or cloud — or to fully reset path reference
Copying to a local drive isolates the path issue from any network problem and gets you working immediately. Going through the portable copy restore process fully resets QB's internal path reference — more thorough than simply copying the .QBW.
1
Copy the .QBW file to a local folder on the C: drive — e.g. C:\QB\. In QuickBooks → File → Open or Restore Company → Open a company file → browse to the local copy → Open.
2
If it opens locally: the network path was the problem. To fully reset the path reference: File → Create Copy → Portable Company File (.QBM) → save it. Then File → Open or Restore Company → Restore a portable file → browse to the .QBM → Next → navigate to the correct server folder → Save. QB restores the file with a fresh, valid path reference.
3
If it still shows 6177 locally: the issue is not the network path — proceed to Method 3. Run a QBDSM scan on the server folder after restoring to rebuild the .ND file.
METHOD 3
Fix Folder Permissions for QBDataServiceUser
After server OS reinstall or domain policy change
1
Right-click the folder containing the company file → Properties → Security tab → Edit → Add. Type QBDataServiceUser followed by the QB version year (e.g. QBDataServiceUser33 for QB 2023) → Check Names → OK. Set permissions to Full Control → Apply → OK.
2
Also grant Full Control to the Windows users who need QB access. Restart QB and try opening the file. Version reference: QB 2021 = QBDataServiceUser31 · QB 2022 = QBDataServiceUser32 · QB 2023 = QBDataServiceUser33 · QB 2024 = QBDataServiceUser34. If unsure which version you have, press F2 in QB → Product Information → note the version year.
METHOD 4
Delete the .ND File and Run QBDSM Scan
Corrupted or stale network descriptor
1
On the server, open File Explorer → navigate to the company file folder → find YourCompanyFile.QBW.ND → right-click → Delete. This does not affect your data. The .ND contains only network address configuration.
2
Tool Hub → Network Issues → QuickBooks Database Server Manager → Scan Folders → add the company file folder → Start Scan. QBDSM creates a fresh .ND file with the correct current server address. Retry opening the company file from workstations.
METHOD 5
Reconfigure Multi-User Hosting
6177 in multi-user mode only — opens in single-user
1
On each workstation: QB → File → Utilities. If "Stop Hosting Multi-User Access" shows → click it. Repeat on all workstations until all show "Host Multi-User Access" (hosting OFF on workstations). On the server: confirm "Stop Hosting Multi-User Access" shows (hosting ON). Then: File → Utilities → Stop Hosting Multi-User Access → Yes → immediately: File → Utilities → Host Multi-User Access → Yes. This resets the hosting configuration. Run a QBDSM scan afterwards. Retry from workstations.
METHOD 6
Run QuickBooks File Doctor
All path methods tried — deeper network or file issue
1
Tool Hub → Company File Issues → Run QuickBooks File Doctor. Select your company file → Check your file and network → Continue → enter QB admin password → run (10–15 min). File Doctor diagnoses and repairs deeper network configuration and file access issues that the manual path methods cannot reach. Use this only after Methods 1–4 have not resolved the error — running File Doctor for a simple path error (where Method 1 would have worked) does not fix the underlying location problem. If File Doctor resolves the issue, create a backup immediately.
Quick Reference
| Your situation |
Likely cause |
Start with |
| File was recently moved, folder renamed, or server renamed |
Stale memorised path |
Method 1 — open from current location |
| File on network, NAS, or cloud — or path needs full reset |
Network path or stale path reference |
Method 2 — local copy + portable restore |
| After server OS reinstall or domain policy change |
Folder permissions reverted |
Method 3 — fix QBDataServiceUser permissions |
| File hasn't moved but 6177 appeared — multi-user environment |
Stale .ND file |
Method 4 — delete .ND + QBDSM scan |
| 6177 in multi-user only, opens fine single-user |
Hosting misconfiguration |
Method 5 — reconfigure hosting |
Frequently Asked Questions
How is Error 6177 different from Error 6000-83?
Both prevent the file from opening, but they fail at different layers. Error 6177 is a path navigation failure — QB cannot reach the location it has memorised for the file. The file exists and is intact, but QB can't navigate to it. Error 6000-83 is a file read failure — QB reached the location successfully but cannot open or read the file itself. Fix 6177 by correcting the path. Fix 6000-83 with File Doctor and Verify/Rebuild. Applying File Doctor to a 6177 error without fixing the path first treats the wrong layer and wastes time.
Error 6177 keeps coming back after I fix it — why?
Recurring 6177 after fixing usually traces to one of three things. A desktop shortcut or Windows startup entry still points to the old path — every time QB opens via that shortcut, it tries the old memorised path and fails. Update or delete the shortcut and open QB from the Start menu instead. A cloud sync service is periodically moving or locking the file — OneDrive, Dropbox, or Google Drive sync can temporarily rename or lock the file during sync, producing intermittent 6177. Move the file permanently to a non-synced local or server path. Or a mapped drive letter is changing — if the network drive letter changes on restart, QB can't find the file at the previously registered path. Fix the drive mapping to use a consistent static letter or UNC path.
Can I store the company file on OneDrive to share with my accountant?
No — Intuit explicitly does not support storing active .QBW files on cloud-synced folders like OneDrive, Dropbox, or Google Drive. These services sync files in the background using non-standard file locking that conflicts with how QB writes data continuously during a session. The result is errors including 6177 and, in some cases, data corruption when two sync processes try to write the file simultaneously. To share your file with an accountant, use QB's built-in Accountant Copy feature (File → Send Company File → Accountant's Copy), or export specific reports as PDFs for review.
Related QuickBooks Company File Errors
Error 6177 Persisting After Path Correction and QBDSM Scan?
Let QuickFix Bookkeeping Restore Your Company File Access.
Certified Intuit ProAdvisors · QuickBooks Network Specialists
Persistent 6177 after path correction and QBDSM scans often points to a deeper network configuration or permission issue. Our certified ProAdvisors diagnose and resolve QuickBooks file access errors in a single session.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Company file access restored fast.
