PerpetualBooks
Sunset TimelineKeep It RunningBy VersionError CodesHacksPlaybooksDownloads Start with the survival guide

QuickBooks Error -6144, -82 -- Damaged Network Descriptor or Database Service

Last reviewed 2026-07-07 4 min read

Error -6144, -82 blocks company file access over a network; our engineers walk through rebuilding the .ND file and restarting the database service to restore connectivity.

When QuickBooks Desktop displays error -6144, -82, the application cannot establish a connection to the company file stored on a network share or in a multi-user environment. Our engineers have resolved this error across thousands of company files, and in nearly every case the root cause is a damaged network descriptor (.ND) file, a mismatched transaction log (.TLG) file, or a stopped QuickBooksDB service. The steps below walk through each trigger scenario from most to least common.

What the Error Message Says

The full dialog typically reads:

"QuickBooks has encountered a problem and needs to close. We apologize for the inconvenience. Error codes: (-6144, -82)"

In some configurations the message may also include: "An error occurred when QuickBooks tried to access the company file." The error appears at the moment you attempt to open or switch to the company file.

What the Code Means

The -6144 series indicates that QuickBooks cannot reach the company file through the QuickBooks Database Server Manager. The -82 sub-code specifies that the failure occurs at the network descriptor level — the .ND file that tells QuickBooks where the company file lives and which server is hosting it. When that descriptor is missing, corrupted, or points to an incorrect path, QuickBooks cannot negotiate the database connection and returns the paired code.

What Triggers It

  • The .ND file is corrupted, stale, or references a previous server path
  • The QuickBooksDBXX service (where XX matches your version year) is stopped or crashed
  • The .TLG file is out of sync with the .QBW file after an improper shutdown
  • The company file folder lost its Windows sharing or folder permissions after an update
  • Multiple versions of QuickBooks Database Server Manager are installed and conflicting

How to Fix It

Scenario 1: Rebuild the .ND file (most common fix)

  1. Close QuickBooks on all workstations.
  2. On the computer hosting the company file, locate the folder containing your .QBW file.
  3. Find the file with the same name as your company file but a .ND extension (for example, MyCompany.ND).
  4. Right-click the .ND file and rename it to MyCompany.ND.OLD.
  5. Open the Start menu, search for QuickBooks Database Server Manager, and open it.
  6. Click the Scan Folders tab, then Add Folder and select the folder containing your company file.
  7. Click Scan. The Server Manager generates a fresh .ND file.
  8. Open QuickBooks and try to open the company file again.

Scenario 2: Restart the QuickBooks Database Server service

  1. Press Windows + R, type services.msc, and press Enter.
  2. Scroll to QuickBooksDBXX (the number matches your QuickBooks version — for example, QuickBooksDB33 for 2023).
  3. Right-click the service and select Restart. If Restart is greyed out, select Start.
  4. Confirm the Startup type is set to Automatic. If it is not, right-click the service, select Properties, change the startup type, and click OK.
  5. Attempt to open the company file.

Scenario 3: Rename the .TLG file

  1. Close QuickBooks on all machines.
  2. On the host computer, navigate to the company file folder.
  3. Locate the .TLG file matching your company file name (for example, MyCompany.TLG).
  4. Right-click and rename it to MyCompany.TLG.OLD.
  5. Open QuickBooks and attempt to open the company file. QuickBooks creates a new .TLG automatically.

Scenario 4: Verify folder permissions and Windows sharing

  1. On the host computer, right-click the folder containing the company file and select Properties.
  2. On the Sharing tab, confirm the folder is shared and that the user accounts needing access are listed.
  3. On the Security tab, confirm that the user QBDataServiceUserXX has Full Control.
  4. Add or adjust permissions as needed, then attempt to open the file from a workstation.

Scenario 5: Remove conflicting Database Server Manager versions

  1. Open Control Panel and go to Programs and Features.
  2. Look for multiple entries of QuickBooks Database Server Manager with different version years.
  3. Uninstall every version that does not match your currently installed QuickBooks Desktop year.
  4. Reboot the computer and run a fresh folder scan in the correct Database Server Manager.

How to Prevent It Recurring

  • Run a Scan Folders operation in Database Server Manager after every QuickBooks update or upgrade
  • Set the QuickBooksDBXX service to Automatic startup so it recovers after reboots
  • Avoid force-closing QuickBooks or powering off the host computer while the company file is open
  • Keep only one version of Database Server Manager installed on the host at any time
  • Schedule a monthly reboot of the host server to clear orphaned database locks before they accumulate
Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.

Start with the survival guide Browse error codes