Fix QuickBooks Desktop Error -6177, 0 (Company File Path)

Last reviewed 2026-07-03 3 min read

QuickBooks Desktop error -6177, 0 blocks access to your company file. Learn what this -6000 family code means and how to fix the file path or damage yourse

When QuickBooks Desktop throws error -6177, 0, it usually means the program is struggling to locate or open your company file using the saved folder path. This error is part of the broader -6000 series—a family of company-file errors in QuickBooks Desktop. Whether you are running a current version or keeping an older, discontinued version of Desktop alive offline, these steps will help you regain access to your data without needing an upgrade.

What Error -6177, 0 Means

In plain English, this specific code indicates a path or folder permission issue. QuickBooks knows the company file exists, but it cannot properly read the directory structure to open it. This often happens when the file was recently moved to a new folder, saved to an external or network drive that is temporarily disconnected, or when Windows folder permissions have changed.

Common Causes

Moved or missing files: The .qbw file was dragged to a new location, breaking the saved shortcut path.
Network or drive issues: The file is hosted on a network drive, NAS, or USB drive that is offline or mapped to a different drive letter.
Damaged configuration files: The QuickBooks Network Descriptor (.ND) or Transaction Log (.TLG) files are corrupted.
Folder permissions: Windows updated or changed user permissions, blocking QuickBooks from reading the folder.

How to Fix It Yourself

Follow these steps in order. They apply to QuickBooks Desktop Pro, Premier, and Enterprise.

Open a Local Copy: If your file lives on a network or external drive, copy the .qbw file directly to your local Desktop (or a local C:\ folder). Open it from there. If it opens successfully, the original folder or network path is your culprit. You can move the file back to the shared folder later and reconfigure your multi-user setup.
Rename the .ND and .TLG Files: These configuration files tell QuickBooks how to find the file on a network. If they are corrupted, QuickBooks will fail to open the company file. Navigate to the folder containing your .qbw file. Find the files with the same name as your company file but ending in .ND and .TLG. Right-click each and rename them (e.g., add .OLD to the end). QuickBooks will automatically recreate these files the next time you open the company file.
Rescan with Database Server Manager: If you rely on multi-user mode, you must let QuickBooks rebuild the network path. Open QuickBooks Database Server Manager on the computer acting as your server. Go to the Scan Folders tab, select the directory where your company file is stored, and click Scan.
Run Verify and Rebuild: If the file still will not open, or if you suspect data corruption, open the local copy of your file (from Step 1). Go to File > Utilities > Verify Data. If QuickBooks finds issues, run Rebuild Data to repair the structural damage.

Preventing Future -6000 Errors

To keep your Desktop environment stable, avoid dragging and dropping your company file to new locations. If you need to move it, use the Windows mapped network drive settings to ensure the drive letter never changes. Run the Database Server Manager scan any time you move your company file or update your workstation hardware.

When the Company File Itself Is Damaged

If you have renamed the .ND and .TLG files, run a Database Server Manager scan, and still cannot open the file—even from a local folder—the .qbw file itself is likely severely corrupted. At this point, restoring from a recent .qbb backup is your best first step. If your backups are also throwing -6000 series errors or failing to restore, you will need advanced QuickBooks company file repair to extract and rebuild the damaged data tables.