Fix QuickBooks Desktop Error -6000 -83: Open Your Company File Again

QuickBooks error -6000 -83 blocks access to your company file. Learn what causes this -6000 family error and how to fix it yourself to keep your Desktop ru

When you try to open, back up, or restore your company file in QuickBooks Desktop and see error -6000 -83, it means the software cannot access your data. This is part of the broader -6000 error family. The good news is that this usually points to a communication, permission, or network issue rather than a destroyed file. You can almost always resolve it yourself and keep your Desktop running exactly as it is.

The -6000 Error Family

Error -6000 -83 belongs to a larger group of company-file access errors (including -6000 -77, -6000 -80, -6000 -304, and -82). While the last two digits specify the exact trigger, the overarching cause across the family is the same: QuickBooks is being blocked from reading the data by the operating system, the network, or a damaged configuration file. If you are seeing a slightly different -6000 code, the troubleshooting steps below will generally apply to your situation as well.

Common Causes of -6000 -83

Before fixing the error, it helps to know why it happens. The most frequent triggers are:

• Network Data (.ND) or Transaction Log (.TLG) files are damaged: These configuration files act as bridges allowing QuickBooks to open the company file. If they are corrupted, access fails.
• Incorrect folder permissions: Windows is blocking QuickBooks from reading the folder where your company file is stored.
• Database Server Manager is out of sync: QuickBooks Database Server Manager is not running, or it stopped scanning the folder after a recent Windows update.
• Firewall or antivirus blocking: Your security software is mistakenly treating QuickBooks as a threat and severing the connection.
• The company file itself is damaged: This is the least common cause, but a severely corrupted .qbw file will throw a -6000 error.

How to Fix Error -6000 -83

Work through these steps in order, checking if the file opens after each one.

1. Test a Local Copy: If your company file is stored on a server or another computer, copy the .qbw file and paste it directly onto your local Desktop. Open it from there. If it opens successfully, the problem is definitely your network, folder permissions, or firewall—not your data.
2. Rename the .ND and .TLG Files: Navigate to the folder containing your company file. You will see files with the exact same name as your company file but ending in .ND and .TLG. Right-click each one and rename them (for example, add .OLD to the end, making it companyfile.qbw.ND.OLD). QuickBooks will automatically rebuild fresh, undamaged versions of these files the next time you open your company data.
3. Rescan with Database Server Manager: Open the Windows Start menu, find QuickBooks Database Server Manager, and run it. Select the folder where your company file is stored and click Scan. This forces QuickBooks to re-recognize the file over your network.
4. Run Verify and Rebuild Data: If the file still will not open, or if it opens but behaves erratically, open the file (if possible), go to the File menu, select Utilities, and choose Verify Data. If QuickBooks finds problems, it will prompt you to run Rebuild Data.

These steps are family-general and work safely across QuickBooks Desktop Pro, Premier, and Enterprise, including older or discontinued versions. You do not need an active Intuit support subscription to use built-in tools like Database Server Manager or the Verify/Rebuild utilities.

How to Prevent It from Recurring

To keep error -6000 -83 from coming back, make sure the Windows user account logged into the computer has full read/write access to the folder where the QuickBooks data lives. If you use a third-party antivirus, check its settings and add an exception for the QuickBooks executable files and your company file folder. Finally, run the QuickBooks Database Server Manager scan whenever you update Windows or move your company file to a new location.

When the Company File Itself is Damaged

If you have renamed the .ND and .TLG files, run a Database Server Manager scan, and successfully opened a local copy on your Desktop—but the file still throws errors or refuses to open—your .qbw data is likely physically damaged. When the built-in Rebuild Data utility fails to fix the corruption, you will need to restore from your most recent manual backup. If a good backup is not available, specialized repair tools can extract the data directly from the damaged file. For severe cases of company file corruption, you can explore our QuickBooks file repair options to salvage the database without needing to upgrade or start over.