September 5, 2026

QuickBooks Desktop -6000 errors: how to tell a network problem from a damaged file before you touch anything

The short answer: a -6000, xxx error means QuickBooks Desktop could not open the company file, and Intuit’s own table sorts the codes into four causes: the file is being hosted from the wrong machine, the small configuration files beside it (.ND and .TLG) are stale or damaged, the QuickBooks installation itself is broken, or the company file is genuinely damaged. Three of those four are fixed without touching the data. So the first job is not to repair the file; it is to run the two or three tests that tell you which of the four you have. Do them in the order below, taken from Intuit’s -6000 article as updated on 5 August 2026, and you will usually be back in the file in under an hour. If the tests point at file damage, stop and read the last section before you run a rebuild.

What the codes mean, grouped by cause

Intuit publishes one table of -6000 series codes with a probable cause for each. Grouping it by cause is more useful than reading it by number.

Two things stand out. Only one cause in that table is the company file, and Intuit’s own step one for every code is to update QuickBooks to the latest release before doing anything else. Wherever you are, the same Database Server Manager and the same .ND and .TLG files sit beside the file, so the fix path does not change with the regional edition.

Intuit’s order, and why it is that order

Intuit’s article runs: update QuickBooks, then run QuickBooks File Doctor from the Tool Hub (version 1.6.0.8 at the time of writing; the “Check your file” option, with the admin password), and only then branch on whether you open the file locally or over a network. That order is deliberate. File Doctor fixes network and configuration problems as well as light file damage, and it does not need you to know which one you have. Run it before you form a theory.

If File Doctor does not clear the error, the branch matters, because the same three tests appear in both branches with one difference.

The three tests that separate the four causes

Test 1: rename the .ND and .TLG files. In the folder holding the company file, rename company_file.qbw.nd and company_file.qbw.tlg by adding .OLD to each. Intuit is explicit that this loses no data; QuickBooks recreates both when the Database Server Manager scans the folder or the file is opened. If the file now opens, the cause was configuration, and you are done. On a network, this step is followed by a Database Server Manager scan from the Tool Hub’s Network Issues tab; on a single PC it is not.

Test 2: open a sample company file. From the No Company Open window, open any sample file. If the sample throws the same error, the problem is the installation, not your data, and the fix is a repair of QuickBooks itself. If the sample opens, your installation is fine and the problem is either the location or the file.

Test 3: copy the .QBW to the desktop and open it from there. Hold Ctrl while starting QuickBooks to reach the No Company Open window, then open the copy. If the copy opens, the original location is the problem: folder permissions, a path Intuit says must be under 210 characters, or a folder buried too deep. If the copy still fails, and the sample opened, you now have evidence of file damage.

On a network there are three more checks before you accept that verdict: press F2 on every workstation and confirm under Local Server Information that hosting is off everywhere except the server; on the server, end the QBW32.EXE, qbupdate.exe and QBDBMgr.exe processes as administrator and reopen in multi-user mode; and confirm the folder permissions and firewall exceptions Intuit documents. A single workstation quietly hosting the file causes more -6000 tickets than anything else we see, (the H-series codes that come from the same hosting fault are covered in our H202 and H505 guide) and it costs nothing to fix.

When the tests point at the file

Intuit’s next steps are to restore a backup, and if the backup also fails, to use Auto Data Recovery. Both are legitimate. Both also have a cost that the article does not spell out: a restored backup loses every transaction entered since it was taken, and an Auto Data Recovery pass works from an older copy of the file plus the transaction log, so it too can leave recent work behind. Before you take either step, write down the last transaction you know is in the file and check whether a colleague still has the file open on another machine, because -6087 and -6131 mean exactly that and need no recovery at all.

If the file really is damaged, the question changes from “how do I open it” to “what is the cheapest way to get a clean set of books”. Rebuild Data, File Doctor and ADR all try to repair the structure in place (the Verify-then-Rebuild sequence, and when to stop repairing, is in our Verify and Rebuild guide). They often succeed on a file that is a few years old. On a file that has been condensed several times, carries a decade of history, or is on a version Intuit no longer supports, the repair can succeed technically and still leave lists and balances that do not reconcile. That is when a conversion, into a new QuickBooks file or into another platform, is the better spend: the lists and open items are rebuilt from reports, history is loaded to the depth you choose, and the result is reconciled to the last trial balance you trust rather than to a structure that has already failed once. Our note on what does not convert is the honest scope of that route, and the Desktop to Online page describes the most common destination.

Keeping it from coming back

1. One host. Only the server runs the Database Server Manager with hosting on. Turn hosting off on every workstation and check it after every QuickBooks update.
2. Short path, real folder. Keep the company file in a folder with a path well under 210 characters, on the server’s local disk, not a synced cloud folder.
3. Multi-user discipline. The .TLG mismatch codes (-6190 family) appear when someone opens the file in single-user mode on the server while others are connected. Make that a rule, not a reminder.
4. Update together. Intuit’s step one is update; a server and workstations on different releases produce errors that look like file damage and are not.
5. Verify monthly. Run Verify Data at month end, when the file is quiet, so the first sign of real damage is a log entry rather than a -6000 at 9 a.m. on payroll day.

Frequently asked questions

Does a -6000 error mean my company file is corrupted?

Usually not. Intuit’s table attributes most -6000 codes to hosting, network setup, permissions or the .ND and .TLG configuration files. File damage is the last cause to test for, after renaming the configuration files, opening a sample file and opening a copy from the desktop.

Will renaming the .ND and .TLG files lose data?

No. Intuit states that renaming them loses no QuickBooks data; both files are recreated when the Database Server Manager scans the folder or the company file is opened. The .TLG is a transaction log used for recovery, so keep the renamed copy until the file has opened and been backed up.

Which -6000 codes are specific to multi-user networks?

The hosting family (-6010,-100; -6138,-105; -6210,0; -6189,-83; -6190,-83; -6120,0; -6073,-816; -6000,-832) and the network family (-6000,-82; -6144,-82; -6012,-1061; -6129,-101; -6176,0). If you open the file on the same PC where QuickBooks is installed and see one of these, check that hosting is not switched on locally.

My version of QuickBooks Desktop is discontinued. Can the error still be fixed?

The tests above work on any version, and discontinued versions make up a large share of the support files we see. What changes is the recovery path: Intuit tools are not updated for those releases, so if the tests point at file damage, a conversion into a supported file is often cheaper than a repair that may not hold.

Related service: QuickBooks support, worldwide · UK · Australia · Canada · Gulf