Quick answer

QuickBooks error 6175 (usually shown as -6175, 0) means a hosted company file cannot be opened or multi-user mode cannot start. It commonly follows a failed restore or file copy that left stale network data behind, or a setup where more than one computer hosts the file. Fix hosting first, refresh the support files, then repair the data.

What error 6175 means

Error 6175 is a company-file connection failure. QuickBooks locates the .QBW file, tries to reach the database server that is supposed to be hosting it, and cannot complete the handshake. The message usually appears as -6175, 0 when you open a hosted file or switch to multi-user mode.

Two situations produce it most often. The first is a hosting conflict: a workstation, not the server, claims the company file, so other computers cannot connect. The second is a stale network descriptor after a restore or copy, where the .ND file still points at the old host.

Related code. Intuit documents 6175,0 together with the closely related -6176, 0, and the same hosting and network checks fix both. If a sample company file also fails to open, the QuickBooks installation rather than the company file is damaged, and you need to repair the program.

Symptoms that come with error 6175

  • QuickBooks opens, but the company file stops loading when multi-user mode starts.
  • The error appears on workstations while the server opens the same file normally, or it appears for every user at once.
  • It surfaces right after you restored a backup, replaced a computer, or copied the file to a new folder.
  • Users see Host Multi-User Access or Stop Hosting Multi-User Access in the File → Utilities menu on more than one computer.
  • Hosting status in the F2 Product Information window does not match the computer that stores the file.

Common causes, ranked by how often they occur

  1. More than one computer is hosting the file. A workstation with hosting left on can take the file, and the real server connection fails.
  2. Stale support files after a restore or copy. The .ND file stores the host name, IP address, and port. If it survives a move, it points users at the wrong computer.
  3. The QuickBooks database service is stopped. The Windows service behind Database Server Manager, named QuickBooksDBXX, may be stopped after a Windows update or crash.
  4. Firewall or antivirus blocks the connection. QuickBooks executables need permission to communicate on the network, and security software can block them silently after an update.
  5. Folder sharing permissions changed. Without Full Control for QBDataServiceUserXX, the database service cannot open the file for remote users.
  6. Data damage in the company file. A damaged file can fail during connection before it ever opens.

Before you begin

  • Back up the whole company-file folder. Copy the .QBW, .ND, .TLG, and .DSN files to an external drive or a second computer. Also make a File → Back Up Company backup if the file still opens on any machine.
  • Plan downtime. Every user must be out of the file while you work, so pick a quiet window.
  • Have admin rights on the server and workstations for service, share, and firewall changes.
  • Identify the server — the computer that stores the file — before changing any hosting setting.

Do not rebuild or restore yet. Hosting and support-file problems are the most common causes of 6175, and they are fixed without touching your accounting data. Rebuild and restore come after those checks, using the backup you just made.

How to fix QuickBooks error 6175

1

Close QuickBooks on every computer

Ask every user to close the company file and exit QuickBooks. On the server, open Task Manager with Ctrl + Shift + Esc and check the Details tab for QBW32.exe, QBDBMgrN.exe, and QBUpdate.exe. End any instance you find.

A file held open by a background process behaves exactly like a hosting conflict, so clear these before you change settings.

2

Back up the company-file folder

Copy the folder that holds the .QBW and its companion files to an external drive or another computer. This copy is your recovery point if a later repair or restore goes wrong, and it takes less time than any of the fixes below.

3

Leave hosting enabled on the server only

On each workstation, open QuickBooks without opening the company file and go to File → Utilities. If you see Stop Hosting Multi-User Access, select it. If you see Host Multi-User Access instead, that computer is not hosting — leave it alone and move to the next workstation.

Then open QuickBooks on the server. In File → Utilities, toggle hosting off and back on: select Host Multi-User Access, then Stop Hosting Multi-User Access, then Host Multi-User Access again. This reset clears a wedged hosting state. If only Database Server Manager is installed on the server, skip the toggle and scan the folder in the next step.

4

Restart the QuickBooks database service and rescan the folder

Open QuickBooks Tool Hub and select Network Issues, then QuickBooks Database Server Manager. On the Scan Folders tab, choose Browse, select the folder that holds the company file, and select Start Scan. The scan rebuilds the network descriptor and repairs firewall permissions for the folder.

If the service is stopped, press Windows + R, type services.msc, and select OK. Find QuickBooksDBXX (QuickBooksDB34 for QuickBooks 2024), confirm the startup type is Automatic, and restart it. Then scan the folder again.

5

Rename the .ND, .TLG, and .DSN support files

With QuickBooks closed everywhere, open the company-file folder and find the files with the same base name as the company file and the extensions .ND, .TLG, and .DSN. Rename each by adding .old to the end, so company.qbw.nd becomes company.qbw.nd.old.

These files hold connection and logging information, not accounting data, and QuickBooks recreates them when you open the file or run a scan. This is the key step when 6175 followed a restore or copy. Never copy an old .ND back into the folder.

6

Run Quick Fix my File, then QuickBooks File Doctor

In QuickBooks Tool Hub, open Company File Issues and run Quick Fix my File first. Then select Run QuickBooks File Doctor, choose your company file from the dropdown, select Check your file (middle option only), and enter your QuickBooks admin password.

A scan can take 10–15 minutes on a large file. File Doctor sometimes reports the scan was unsuccessful even when it repaired the problem, so close the tool and try opening the file anyway. The File Doctor walkthrough covers each option.

Back up before data repair. Verify is read-only, but Rebuild replaces the file's internal indexes and a restore replaces the file itself. Confirm your folder copy from step 2 exists before continuing.

7

Run Verify Data, then Rebuild Data if needed

If the company file opens now, run Window → Close All, then File → Utilities → Verify Data. If QuickBooks reports no problems, the file is healthy and you are done with the repair. If it reports that your data has lost integrity, run File → Utilities → Rebuild Data and save the required backup under a new name.

QuickBooks can appear frozen during a rebuild; if the mouse pointer moves, it is working. Verify again when it finishes — two or three passes are normal. If the file will not open at all, skip rebuild and restore from backup, or follow the data damage recovery order.

8

Restore a clean backup in the right order

Restore only after hosting, support files, and File Doctor have all failed. Choose File → Open or Restore Company and select the restore option for a .QBB backup (labeled Restore a Backup File in current releases and Restore a backup copy in older ones). Send the restored .QBW to a local folder on the server — not to a USB drive or a network share — and confirm it opens in single-user mode.

Then move it to the shared company-file folder, have each workstation open it, and run a Database Server Manager scan so a fresh .ND is created for the correct host. Never restore over the working file or copy only the .QBW next to an old .ND; that recreates the condition that caused 6175. If restore fails, see QuickBooks restore failed.

Verify the fix

  1. Open the company file on the server in multi-user mode and confirm it loads without the error.
  2. Open the same file from two workstations and post a test transaction, then delete it.
  3. Press F2 on the server and confirm the Local Server Information section shows hosting active and the correct file path.
  4. Run File → Utilities → Verify Data and confirm it reports no problems.
  5. Create a fresh backup with File → Back Up Company and store it off the server.

If error 6175 persists

Two official checks remain. First, confirm the Windows user QBDataServiceUserXX exists with administrator rights on the server; Intuit's 6175 article lists this as a required fix. Second, open your firewall settings and make sure QBW32.exe, QBUpdate.exe, QBDBMgr.exe, and QBDBMgrN.exe are allowed through on every computer.

If a sample company file also fails to open, the installation is damaged. Repair QuickBooks from Control Panel → Programs and Features: select QuickBooks, choose Repair, and test again. When hosting checks, File Doctor, Verify, Rebuild, and a clean restore all fail, escalate to Intuit support with the exact code, your version, and the steps you completed. If no clean backup exists and the file is damaged, keep the original untouched and ask about Intuit's data recovery service or a professional company file repair rather than repeating rebuilds.

Prevention

  • Keep hosting on exactly one computer — the server — and recheck it before you add a new workstation.
  • Give the server a static IP address so the network descriptor never points at a stale address.
  • Disable sleep and hibernation on the server; a host that sleeps drops every multi-user connection.
  • Restore backups to a local drive on the server, then move the file and rescan the folder.
  • Run Verify Data twice a year and test a restore every quarter; see QuickBooks backup and restore.

Frequently asked questions

Does error 6175 mean I have lost data?

Usually not. The error blocks the connection to the file, not the data inside it. Your transactions stay in the .QBW file. Data loss becomes a risk only if you restore an old backup over the current file or a damaged file cannot be repaired.

Why does 6175 appear right after restoring a backup?

The restore puts the company file in a new location while an old .ND file or an old hosting setting still points at the previous path. Rename the support files, set hosting on the server only, and run a Database Server Manager scan to regenerate them.

Is it safe to rename the .ND and .TLG files?

Yes. They hold connection details and the transaction log for recovery, not your accounting records. QuickBooks rebuilds them automatically. Renaming instead of deleting keeps the originals for troubleshooting if the problem continues.

When should I stop troubleshooting and contact Intuit?

Escalate after you have completed the hosting reset, a Database Server Manager scan, the support-file rename, File Doctor, Verify and Rebuild, and one clean restore — and the error still appears. Bring the exact error code, your QuickBooks version, and a note of the steps you tried.

Sources & further reading