Quick answer

QuickBooks error 6190 (often shown as -6190, 0, -6190, -83, or -6190, 816) means QuickBooks found the company file on the network but could not open it on this computer. The cause is almost always the multi-user setup — hosting on the wrong computer, a stale .ND file, a stopped database service, or blocked access — not the accounting data itself.

What QuickBooks error 6190 means

Error 6190 is a company-file access failure in QuickBooks Desktop, and it belongs to the multi-user family of errors. The full message is usually "An error occurred when QuickBooks tried to access the company file (6190, 816)" or a similar code pair. QuickBooks can see the file, but the connection between the program, the database service, and the file cannot be completed.

The suffix after the comma narrows down the cause, so note it exactly before you start. Intuit lists these -6190 variants in its -6000 series documentation:

VariantWhat Intuit says it meansStart with
-6190, 0Plain connection failure — the same network family as -6175, 0 and -6176, 0Step 2
-6190, -83The company file is hosted by a computer that is not the serverStep 2
-6190, 816 / -6190, -85 / -6190, -82A user is in single-user mode while others need multi-user, or the .TLG and .QBW files do not matchSteps 4 and 5
-6190, 1005Something went wrong when QuickBooks tried to openStep 7

Intuit states that messages like 6189, 816 and 6190, 816 point to the multi-user network, not to your data file — which is why the order below checks hosting, services, and support files first.

Symptoms that come with error 6190

  • A workstation cannot open the file, while the server opens it without trouble.
  • It appears when someone switches to multi-user mode, or when a second user tries to sign in.
  • The dialog may mention that the file "has been opened by another user" or that the folder is read-only.
  • It follows a server restart, a Windows update, a power failure, or an antivirus update.

Common causes, ranked by how often they occur

  1. Hosting left on at a workstation. When two computers claim the file, connections break with a -6190 variant — the most common cause of -6190, -83.
  2. A stale .ND or .TLG file. The .ND file stores the host name and connection details. After a restore, rename, or move, it can point at the wrong computer.
  3. The QuickBooks database service is stopped. The Windows service behind Database Server Manager can stop after a reboot or crash, leaving no host for the file.
  4. Mixed single-user and multi-user activity. One user opening the file in single-user mode blocks everyone else; a mismatched transaction log produces the same 6190, 816 message.
  5. The file path is the problem. A path longer than 210 characters, a mapped drive letter that changed, or a file stored in a cloud-sync folder, on a USB drive, or on a NAS device.

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. If the file opens anywhere, also create a File → Back Up Company backup.
  • Plan downtime. Every user must close the file during these checks, so pick a quiet window.
  • Have administrator rights on the server and the affected workstations for service, share, and firewall changes.
  • Identify the server. Know which computer stores the company file before you change any hosting setting.

Back up before any data repair. Renaming support files is safe, but Rebuild replaces the file's internal indexes and a restore replaces the whole file. Confirm the folder copy above exists before you run either.

How to fix QuickBooks error 6190

1

Close every QuickBooks process everywhere

Ask every user to close the company file and exit QuickBooks. On the server and the failing workstation, open Task Manager with Ctrl + Shift + Esc, check the Details tab, and end any instance of QBW32.exe, QBDBMgr.exe, QBDBMgrN.exe, QBCFMonitorService.exe, and QBUpdate.exe.

A background process holding the file acts like a second user, so clear these first.

2

Make sure only the server hosts the company file

On every 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, the workstation is not hosting — leave it and check the next computer.

On the server, open the file and press F2. In the Product Information window, the Local Server Information section shows hosting status. Toggle it off and back on to clear a wedged state. This resolves most -6190, -83 reports; related failures are covered in the error 6175 guide.

3

Restart the QuickBooks database service on the server

Press Windows + R, type services.msc, and select OK. Find the QuickBooks database service — it is named QuickBooksDB followed by the version number, and later versions may show a different suffix, so confirm the exact name in the list. Set its startup type to Automatic, then right-click it and select Restart.

If it will not start, note the error and reboot the server; a service that stays stopped usually needs a repair installation.

4

Run the Database Server Manager scan

On the server, open the QuickBooks Tool Hub and select Network Issues, then QuickBooks Database Server Manager. Select Browse, choose the folder that holds the company file, and select Start Scan. The scan recreates the network descriptor and repairs firewall permissions for the file automatically.

Intuit's 6190, 816 article also recommends restarting the server, then each workstation, after a recent update or crash.

5

Rename the .ND and .TLG support files

With QuickBooks closed on every computer, open the company-file folder and find the files with the same base name as the company file and the extensions .ND and .TLG — for example company.qbw.nd and company.qbw.tlg. Rename each by adding .old to the end.

These files hold connection details and the transaction log, not accounting data, and QuickBooks rebuilds them on the next scan or open. This is the key step for the mismatch behind most -6190, 816 errors. Never copy an old .ND back into the folder.

6

Test the company file from a local copy

Copy the .QBW file to the desktop or a plain local folder such as C:\QBTest. Hold Ctrl while launching QuickBooks to force the No Company Open window, then select Open or restore an existing company and open the copy.

If the copy opens, the location is the problem. Check that the full path is under 210 characters, replace any mapped drive letter with the UNC path (\\Server\Share\CompanyFile.qbw), and move the file off cloud-sync folders, USB drives, and NAS devices. Multi-user problems that survive these checks are covered in the multi-user troubleshooting guide.

7

Run Quick Fix my Program, then File Doctor

In QuickBooks Tool Hub, open Program Problems and run Quick Fix my Program. Then open Company File Issues, select Run QuickBooks File Doctor, choose your company file from the dropdown, select Check your file, and enter your QuickBooks admin password.

A scan can take 10–15 minutes, and File Doctor sometimes reports failure even when it repaired the issue, so try opening the file anyway; the File Doctor guide explains each option.

8

Run Verify Data, then Rebuild Data

If the file opens, run Window → Close All, then File → Utilities → Verify Data. If QuickBooks reports no problems, the file is healthy. 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 look frozen during a rebuild; if the mouse pointer moves, it is working. Run Verify again when it finishes — two or three passes are normal. If the file will not open at all, skip the rebuild and restore from backup, or follow the recovery order in the error 6000 guide.

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 Local Server Information shows hosting active and the correct file path.
  4. Run File → Utilities → Verify Data and confirm no problems are reported.
  5. Create a fresh backup with File → Back Up Company and store it off the server.

If error 6190 persists

Right-click the company-file folder, open Properties → Security, and confirm your account and the QuickBooks database service account have Modify or Full control; grant the same rights on the Sharing tab. Confirm the QBDataServiceUserXX account exists with administrator rights on the server.

Check that Windows Firewall allows QBW32.exe, QBDBMgr.exe, QBDBMgrN.exe, and QBUpdate.exe everywhere, and that TCP port 8019 is open on the server. Add the company-file folder as an antivirus exclusion and remove encryption from it.

If a sample company file also fails, repair QuickBooks from Control Panel → Programs and Features and test again. If an Intuit hosting provider hosts the file, ask the provider to restart the service. Escalate after the hosting reset, Database Server Manager scan, support-file rename, File Doctor, and one Verify/Rebuild pass, with the exact code and your version. If no clean backup exists, keep the damaged original untouched and ask about Intuit Data Services or a professional company file repair.

Prevention

  • Keep hosting on exactly one computer — the server — and verify it before adding a workstation.
  • Give the server a static IP address so the .ND file never points at a stale address.
  • Set the QuickBooks database service to Automatic and confirm it is running after every reboot.
  • Disable sleep and hibernation on the server, and store files only on local or shared server drives — never in cloud-sync folders, on USB drives, or on a NAS.
  • Keep every computer on the same QuickBooks version and release, run Verify Data twice a year, and test a restore each quarter.

Frequently asked questions

Does error 6190 mean my company file is corrupt?

Usually not. Intuit states that 6190, 816 points to the multi-user network rather than the data file. If the error survives the hosting and support-file fixes, run Verify Data.

Why does 6190, 816 say someone is in single-user mode when everyone is in multi-user?

QuickBooks believes the file is still open in single-user mode, or the transaction log no longer matches the company file. Ask every user to exit, close background QuickBooks processes, rename the .TLG and .ND files, and scan the folder with Database Server Manager so both are rebuilt.

Why does error 6190 appear on only one workstation?

That points at the workstation rather than the file: hosting accidentally enabled on it, folder or share permissions, antivirus, a stale mapped drive, or firewall settings. Stop hosting on it, reconnect using the UNC path, and test a local copy of the file to confirm the data is fine.

When should I stop troubleshooting and contact Intuit?

Escalate after you have stopped hosting on every workstation, restarted the database service, run a Database Server Manager scan, renamed the support files, run File Doctor, and completed one Verify/Rebuild pass — and the error still appears. Bring the exact error code, your QuickBooks version, and the steps you tried.

Sources & further reading