Fix QuickBooks Desktop Error -6190 -816: Causes and Solutions

Resolve QuickBooks Desktop error -6190 -816, part of the -6000 company-file family. Learn what causes mismatched files and how to fix it yourself.

When you try to open your company file in QuickBooks Desktop and error -6190 -816 appears, it usually means the software cannot verify the file's status on your network. This error is part of the broader -6000 series, which covers general company file access issues. If you are maintaining QuickBooks on your own or running a discontinued version offline, you can resolve this without Intuit support or forced upgrades.

What Error -6190 -816 Means

In plain English, this specific error indicates a mismatch between your actual company file (.qbw) and its corresponding backup or transaction log file (.tlg). QuickBooks uses the .tlg file to track changes until the next backup. If the main file and the log file fall out of sync—often because the file was opened in single-user mode on another machine—QuickBooks locks the file to protect your data, resulting in the -6190 -816 code.

Common Causes

The mismatch or network lock typically happens for a few reasons:

• Another workstation currently has the company file open in Single-User mode.
• You restored a backup (.qbb) but left the older .tlg file in the same folder.
• The QuickBooks Database Server Manager lost track of the file over your local network.
• Your antivirus or firewall temporarily blocked QuickBooks during a background update or scan.

How to Fix It Yourself

Work through these steps in order. They apply generally across QuickBooks Desktop Pro, Premier, and Enterprise.

1. Check for Single-User Mode: Go to every computer on your network. If anyone has QuickBooks open, have them close it or switch the main machine to Multi-User mode. Often, simply closing the program on the other workstation clears the error immediately.
2. Rename the .TLG and .ND Files: QuickBooks will recreate these configuration files automatically if they go missing.
   • Navigate to the folder holding your company file.
   • Find the file ending in .tlg (it will have the same name as your company file). Right-click and rename it to OLDcompanyfilename.tlg.
   • Do the same for the file ending in .nd.
   • Try opening QuickBooks again.
3. Run Database Server Manager: On the computer acting as your server, open the Windows Start menu, find QuickBooks Database Server Manager, and run a scan on the folder containing your company file. This forces the server to recognize the file for multi-user access.
4. Verify and Rebuild Data: If the file opens but you suspect damage, go to the File menu, select Utilities, and run Verify Data. If QuickBooks finds structural issues, run Rebuild Data to attempt an automatic repair.

When the Company File Is Damaged

If you have worked through the network and configuration steps above and QuickBooks still refuses to open the file, the company file itself (.qbw) is likely corrupted. This can happen if a workstation crashed or lost power exactly while QuickBooks was writing to the disk. When standard internal rebuilds fail to fix the -6000 series errors, you will need an advanced utility to repair the underlying database structure. For heavily damaged data, our team provides dedicated QuickBooks company file repair to recover your records safely.

Preventing the Error

To keep your Desktop setup stable long-term, ensure all users close QuickBooks completely at the end of the workday rather than leaving it locked overnight. Configure your antivirus software to exclude the QuickBooks installation directory and your company file folder from active scanning. Finally, run the Database Server Manager scan any time you move your company file to a new folder or change your local network setup.