Why 6177 is different from 6000-83: Both errors prevent QB from opening the company file, but they fail at different layers. 6000-83 means QB reached the file but can't read it (file damage, bad extension, or permissions on the file itself). 6177 means QB can't even reach the path — the location doesn't exist or is inaccessible before QB can attempt to open the file. Fix 6177 by fixing the path. Fix 6000-83 by fixing the file. Running File Doctor for a 6177 path error won't fix the underlying location problem.

Error code

6177, 0

6xxx Series · Path / Access

Related: -6000 -83 · -6000 -82 · -6150

What it means

Error 6177 means QuickBooks is unable to use the stored path to open the company file. QuickBooks memorises the location of each company file it has opened. If that location changes — the folder is moved, renamed, the drive letter changes, or network access is lost — QuickBooks cannot navigate to the file and returns 6177. The file itself is almost always intact.

Your data is almost certainly safe. Error 6177 is a navigation failure — QuickBooks can't find the path to the file, not that the file is damaged or deleted. Once the path is corrected, QuickBooks opens normally.

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 from File → Open or Restore resolves this instantly.

Network Share or Drive Letter Changed

The mapped network drive letter used to access the server changed (e.g. from Z: to Y:), or the UNC path to the server changed after a network reconfiguration or server rename. QB cannot reach the old path.

File Stored in Unsupported Location

The company file is stored in a cloud-synced folder (Dropbox, OneDrive, Google Drive) or a NAS device that QuickBooks does not support. These locations use non-standard file access methods that QB cannot reliably navigate, producing 6177.

Folder Permission Change

The Windows folder permissions on the company file directory were changed — common after a server OS reinstall, a domain policy update, or a group policy change. The QBDataServiceUser or the logged-in user no longer has Read/Write access to the folder.

Corrupted or Stale .ND File

The Network Descriptor (.ND) file that tells QuickBooks how to reach the company file over the network contains an outdated or incorrect path. Deleting and regenerating the .ND via QBDSM scan fixes this.

Hosting Misconfiguration

In a multi-user setup, QuickBooks on a workstation is trying to open the file directly rather than routing through the server. Incorrect hosting settings cause QB to attempt a local path that doesn't exist on the workstation.

METHOD 1 Open the File Directly from Its Current Location Under 2 minutes — try this first

When QuickBooks 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.

METHOD 2 Copy the Company File to a Local C: Drive and Test File on network, NAS, or cloud sync folder

If the file is on a network share, NAS, or cloud-synced folder that QB can't reliably navigate, copying it locally isolates the path issue from any file damage and gets you working immediately.

METHOD 3 Fix Folder Permissions for QBDataServiceUser After server OS reinstall or domain policy change

QuickBooks uses a Windows service account (QBDataServiceUser) to access company files on the server. If this account's folder permissions were removed or restricted, QB cannot open the file and returns 6177.

METHOD 4 Delete the .ND File and Run QBDSM Scan Corrupted or stale network descriptor

The .ND (Network Descriptor) file tells QuickBooks where the company file lives on the network. If its contents are stale or corrupted, QB cannot navigate to the file. Deleting it and letting QBDSM regenerate it is a clean fix.

METHOD 5 Run QuickBooks File Doctor All path methods tried — underlying network or file issue

If the file path is correct, permissions are set, and the .ND was regenerated but 6177 persists, File Doctor addresses deeper network configuration and file access issues.

How is Error 6177 different from Error 6000-83? Both prevent the file from opening.

The failure point is different for each. Error 6177 is a path navigation failure — QuickBooks 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 (Method 1) or copying the file locally (Method 2). Fix 6000-83 with File Doctor and Verify/Rebuild. Applying -83 fixes to a 6177 error (running File Doctor without fixing the path first) treats the wrong layer and wastes time.

Can I store my company file on OneDrive or Dropbox to share it 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 QuickBooks writes data continuously during a session. The result is errors including 6177 and 6000-83, and in some cases data corruption when two sync processes try to write the file simultaneously. To share your file with an accountant, use QuickBooks' built-in Accountant Copy feature (File → Send Company File → Accountant's Copy), or invite them as a user via QuickBooks Online if you are using the online version.

6177 keeps coming back after I fix it — what is causing the recurring error?

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 again. 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 be consistent using a static drive letter or a UNC path.