Fix QuickBooks Desktop Error -6147 0 When Opening or Restoring

Last reviewed 2026-07-03 4 min read

Resolve QuickBooks Desktop error -6147 0 so you can restore backups and open company files. Step-by-step fixes for the -6000 error family that work offline

When you try to open a company file or restore a backup in QuickBooks Desktop and the process fails with error -6147 0, it usually means the program lost its connection to the data file or encountered something it could not read. The error is part of the broader -6000 series—a family of company-file errors in QuickBooks Desktop. If you are maintaining an older, discontinued version of Desktop, the good news is that these errors are structural and local. You can resolve them entirely on your own machine without any Intuit support or forced upgrades.

What Error -6147 0 Means

In plain English, this code means QuickBooks attempted to access your company file (or a backup file) but was blocked by a network glitch, a damaged configuration file, or data corruption within the backup itself. Because it is a -6000 family error, the underlying mechanics are the same as similar codes like -6190, -6144, or -6189. QuickBooks relies on several hidden helper files to locate and open your data; if those helpers are missing, mismatched, or damaged, the software throws a -6000 error.

Common Causes

Damaged configuration files: QuickBooks uses .ND (Network Descriptor) and .TLG (Transaction Log) files to communicate with your data. If these become corrupted, QuickBooks cannot find or open your company file.
Folder permissions: Windows might be blocking QuickBooks from reading the folder where your backup or company file is stored.
Incomplete or interrupted backup: If the backup file (.QBB) was created while the program was closing or during a sudden power loss, the file may be incomplete.
Company file corruption: The .QBW or .QBB file itself has structural damage preventing it from opening normally.

How to Fix Error -6147 0

Work through these steps in order. They apply to QuickBooks Desktop Pro, Premier, and Enterprise, whether you are on a current or discontinued version.

1. Move the file to a local drive

If you are trying to restore a backup from a USB drive, network share, or cloud storage folder (like OneDrive or Google Drive), copy the backup file (.QBB) directly to your computer's Desktop or a local C:\ folder. Network latency and sync locks frequently cause -6000 errors. Try restoring it from the local location.

2. Rename the .ND and .TLG files

QuickBooks will automatically recreate these configuration files if they go missing.

Open the folder containing your company file (.QBW).
Find files ending in .ND and .TLG that share the exact same name as your company file.
Right-click each one and select Rename. Add the word OLD to the end (e.g., change CompanyFile.ND to CompanyFile.ND.OLD).
Open QuickBooks and try to open or restore your file again.

3. Rescan with Database Server Manager

If you are running QuickBooks in multi-user mode, the network database might simply need a refresh.

Open the Windows Start menu and search for QuickBooks Database Server Manager.
Select Scan Folders.
Browse to the folder containing your company file and click Scan.
Once the scan finishes, open QuickBooks and attempt your action again.

4. Run Verify and Rebuild Data Utility

If the file opens but you still get warnings, or if you want to check the file's health, use QuickBooks' built-in repair tools.

With your company file open, go to the File menu, hover over Utilities, and select Rebuild Data.
When prompted, create a backup as part of the rebuild process.
Once the rebuild finishes, go back to File > Utilities and select Verify Data. This will check for any remaining structural damage.

Preventing the Error from Recurring

To keep your Desktop installation stable, always store your active company file on a local drive rather than in a cloud-synced folder. When creating backups, save them directly to a local folder first before copying them to an external drive for safekeeping. Running the Verify Data utility once a month catches minor data list issues before they turn into errors that block you from opening the file.

When the Company File Itself is Damaged

If you have renamed the .ND and .TLG files, moved the data to a local drive, and the file still throws error -6147 0, the backup or company file itself is likely structurally damaged. When the internal database tables are broken, QuickBooks simply cannot read the file. In this scenario, you will need to repair the damaged QuickBooks company file to extract your data and get your books running smoothly again on your existing Desktop setup.