Quick answer

QuickBooks error 6147 means QuickBooks could not access the company file you selected, usually in a multi-user setup. The file path, the .ND network file, hosting settings, or folder permissions are the common blockers. Work through path, hosting, and permissions first, then run Verify and Rebuild only if the file itself is damaged.

What QuickBooks error 6147 means

QuickBooks error 6147 is an access failure, not a missing-file message. QuickBooks found the file or its reference but could not complete the connection and open it. Intuit lists -6147 among the errors QuickBooks File Doctor repairs, and its 6000-series reference ties -6147, 0 to opening a company file or restoring a company backup (.QBB).

In multi-user mode the failure usually happens during path resolution. QuickBooks reads the .ND file — the network data file next to the company file — to learn which server, IP address, and port to contact. If that information is stale, the connection fails. Intuit's hosting documentation lists three conditions that must all be true before QuickBooks Desktop allows access:

  • Windows file permissions: the signed-in user needs Full control to view, open, and modify the file.
  • Database server mode: the database server must be able to open the company file.
  • QuickBooks user login: each user needs a QuickBooks login and password.

Error 6147 can also appear on a single computer, most often while restoring a backup from a network folder or external drive.

Symptoms that point to error 6147

  • The error appears right after you select the company file on a workstation, while the server seems fine.
  • Only one computer fails, or every workstation fails after the server restarts or changes its IP address.
  • The dialog appears during a .QBB restore, even though the backup is recent and healthy.
  • The file opens locally on the server but not over the network, while a sample file opens normally.

Common causes, ranked by how often they appear

  1. A stale or damaged .ND file. It points at an old server name, IP address, port, or path. Intuit notes a company file will not open if the .ND file is damaged or incorrect, or if the .QBW was moved without moving the .ND.
  2. Hosting is set up on the wrong computer. When a workstation hosts multi-user access instead of the server — or hosting is off on the server — connections fail with access errors.
  3. The path no longer resolves. Mapped drive letters get reassigned, shares get renamed, and DNS records change. A workstation can fail to resolve the server name while the IP still works.
  4. Permissions or the database service changed. A domain change, new Windows profile, Windows update, or rebuilt server can strip Full control from the user or the QBDataServiceUserXX account, and the QuickBooksDBXX service or its firewall port may be stopped or blocked.
  5. The company file or .TLG file is damaged. If the network is healthy and other files open, the file itself may have lost integrity. Cloud-sync folders, USB drives, and NAS devices are unsupported locations that cause this.

Back up before you repair. Have every user sign out, then copy the entire company-file folder — .QBW, .TLG, and .ND files together — to a local folder or external drive. Renaming support files is safe, but Rebuild changes data files, so the copy is your rollback point.

Before you begin

  • Time: 30–60 minutes, plus 10–15 minutes if File Doctor scans the file.
  • Access: administrator rights on the workstation and the server, plus the QuickBooks admin password.
  • Setup: know which computer is the server (it stores and hosts the company files) and which ones are workstations.

How to fix QuickBooks error 6147

1

Identify the scope and the exact error text

Find out whether one workstation fails or all of them do, and whether the error appears when opening the file or when restoring a .QBB. A single failing computer points at a local mapped drive, permissions, DNS, or hosting enabled on that PC. If every computer fails, treat it as a server problem: hosting, the database service, the shared folder, or the file itself. Note the suffix Intuit documents, -6147, 0.

2

Test the company file locally on the server

On the server, open QuickBooks and try the file from the server's own hard drive: File → Open or Restore Company → Open a company file. If it opens locally but not from a workstation, the data is healthy and the problem is the network path, permissions, or hosting. Copy the folder to C:\QBData and open that copy if you normally work on a different computer.

3

Rebuild the .ND network data file

The .ND file is a 1 KB text configuration file named after the company file, such as company.qbw.nd. It stores the server IP address, port, hosting state, and the path to the .QBW. When it is stale, QuickBooks contacts the wrong place and 6147 follows. On the computer that stores the files, search the folder for *.nd and rename each one by adding .OLD (for example, company.qbw.nd.OLD). Do not delete the .QBW; the support files are recreated automatically.

4

Regenerate the .ND file with Database Server Manager

On the server, open the Start menu, type Database, and open QuickBooks Database Server Manager. On the Scan Folders tab, select Browse, add the folder that holds your company .QBW files, and select Start Scan. A fresh .ND file is created when the scan finishes. Database Server Manager cannot monitor mapped drives, so point it at a local path. If the scan will not run or no .ND appears, restart the service for your year in services.msc — QuickBooksDB34 (2024), QuickBooksDB33 (2023), or QuickBooksDB32 (2022) — confirm QBCFMonitorService is running, then rescan.

5

Make sure only the server hosts multi-user access

On every workstation, open QuickBooks but not the company file. Go to File → Utilities. If you see Stop Hosting Multi-User Access, select it and confirm. If you see Host Multi-User Access, leave it and check the next computer. Then do the same on the server, resetting the setting by selecting Stop Hosting Multi-User Access, then Host Multi-User Access. Only the server that stores the files should host. See the multi-user troubleshooting guide for the full reset.

6

Resolve the network path by name and by IP

Replace mapped drive letters with the full UNC path, for example \\Server\Share\CompanyFile.qbw, because Windows can reassign letters after a reboot or a new device. On the failing workstation, press Windows + R, type cmd, and run ping ServerName, then ping the server's IP address. If the IP replies but the name does not, the problem is name resolution, not QuickBooks. The missing company file steps cover this test and wildcard searches.

7

Check folder and share permissions

On the server, right-click the company-file folder and open Properties → Security. Confirm the signed-in user and the QuickBooks database service account (QBDataServiceUserXX) both have Full control. On the Sharing tab, confirm the share grants the same access over the network; the stricter layer wins. If the folder was moved or restored recently, re-check permissions first, and avoid encryption or "protected folder" tools on the folder that holds the .QBW.

8

Run Quick Fix my File and File Doctor

Download the current QuickBooks Tool Hub on the computer that stores the file. Open Company File Issues and select Quick Fix my File, then Run QuickBooks File Doctor. Choose the company file, select Check your file, and enter the admin password. File Doctor is Intuit's documented tool for -6147 and runs a network and firewall mini-repair alongside the file check. A scan can take 10–15 minutes and may report "unsuccessful" even when it fixed the issue. The File Doctor guide walks through the screens.

9

Run Verify Data, then Rebuild Data

Only after the path, hosting, permissions, and .ND file are healthy should you treat this as data damage. Open the file in single-user mode, go to Window → Close All, then File → Utilities → Verify Data. If QuickBooks reports no problems, the file is clean and 6147 was environmental. If it reports lost integrity, go to File → Utilities → Rebuild Data. QuickBooks requires a backup before rebuilding — save it under a new name. Run Verify again afterward; two or three passes are normal. If rebuild cannot repair it, follow the data damage recovery order.

Verify the fix

  1. Open the company file on the server, then on one workstation, in multi-user mode.
  2. Press F2 on each computer and confirm Local Server Information shows the correct server and hosting state.
  3. Run File → Utilities → Verify Data and confirm it reports no problems.
  4. Create a fresh backup and confirm the company-file folder contains a regenerated .ND file.

If error 6147 persists

If one workstation still fails while others work, rebuild that computer's network stack: update the network adapter driver, run ipconfig /flushdns, and remove mapped drives that point at the old server. If the failure follows the file to every computer, the file is the common factor and professional company-file repair is the next step. If a second File Doctor pass and a clean rebuild both fail, restore the newest backup that opens cleanly and keep the damaged file untouched for Intuit Data Services.

Prevention

  • Give the server a static IP address, disable sleep on it, and keep it powered on during work hours.
  • Access the company file by UNC path, share the folder with Full control for the QuickBooks service account, and rescan in Database Server Manager whenever a file moves.
  • Keep only the server hosting multi-user access, and check workstations after any QuickBooks update.
  • Keep every computer on the same QuickBooks version, store files on a local or server hard drive, and run Verify Data twice a year.

Frequently asked questions

Does error 6147 mean my company file is corrupt?

Usually not. Error 6147 describes an access or connection failure, and in multi-user setups the cause is normally the .ND file, hosting, permissions, or the network path. Run File → Utilities → Verify Data to find out whether the file itself lost integrity.

Can I fix error 6147 by renaming the .ND file?

Often, yes. The .ND file is a configuration file, not accounting data, so renaming it is safe. Add .OLD to the extension, then rescan the folder in QuickBooks Database Server Manager to create a fresh file with the correct server, IP, port, and path.

Why does error 6147 appear on only one workstation?

That points at the workstation: a mapped drive that changed letters, DNS that fails for the server name, permissions that changed, a firewall rule, or hosting accidentally enabled on that PC. Test the file locally on the server, then fix that workstation's path and hosting settings.

What should I do if error 6147 appears while restoring a backup?

Move the .QBB off the network, external drive, or online-storage folder and onto the local hard drive, then restore it with File → Open or Restore Company → Restore a backup copy. Verify the restored file before moving it back to the server.

Sources & further reading