QuickBooks Error -6143 0 -- Company File Will Not Open After Network or Data Damage

QuickBooks error -6143 0 blocks opening of the company file, usually after a network drop or file damage; here is how to diagnose and clear it.

When QuickBooks Desktop refuses to open a company file and reports error -6143 0, the cause is almost always one of three things: a damaged network connection to a hosted file, a company file that has been corrupted internally, or a folder permission problem on the machine hosting the file. Our engineers treat this as a 6000-series data access error, and in most cases it can be resolved without a full data repair.

What the error message says

The full message typically reads:

"Error -6143, 0: QuickBooks has encountered a problem and needs to close. We are sorry for the inconvenience."

A variation seen in multi-user setups reads:

"Error -6143 0 when opening a company file located on a network share or in multi-user mode."

The error appears at the moment QuickBooks attempts to open the file, before any company data is displayed.

What the code means

The -6143 0 code belongs to the 6000 family, which covers failures to open, access, or communicate with a company file. The first number identifies the general failure class (file access), and the second number, 0, indicates that QuickBooks could not establish a usable connection to the file's database at all. In practice, QuickBooks reached the point where the file should be, but could not open it into a working database session.

What triggers it

  • A network disconnect while the file was open, leaving the database server without a clean close of the file
  • Damage to the company file itself, often after a power loss or an interrupted save
  • Insufficient Windows folder permissions on the computer hosting the file
  • A stale or damaged Network Descriptor (.ND) file pointing QuickBooks at the wrong database server
  • Firewall or antivirus software blocking communication between the workstation and the host
  • Opening the file by double-clicking it from a mapped or synced drive instead of through QuickBooks

How to fix it

Work through these scenarios in order, starting with the most common.

1. Run QuickBooks File Doctor on the affected file

  1. Download and run the QuickBooks Tool Hub, then open the Company File Issues tab.
  2. Select QuickBooks File Doctor and choose the company file from the drop-down list.
  3. Enter the admin credentials for the file and let the scan complete; it can run for some time on larger files.
  4. When it finishes, open the file normally. File Doctor repairs both the network descriptor files and many forms of internal file damage in one pass.

2. Rebuild the network descriptor file

  1. On the computer that hosts the file, close QuickBooks on all workstations.
  2. Locate the folder holding the company file and find the file with the same name as your company file but ending in .ND.
  3. Rename that file so it ends in .OLD instead of .ND.
  4. Open QuickBooks on the host and open the company file. QuickBooks rebuilds the descriptor automatically.
  5. Switch to multi-user mode on the host, then reopen the file from each workstation.

3. Verify and repair folder permissions on the host

  1. On the host computer, right-click the folder containing the company file and open Properties, then the Security tab.
  2. Confirm that the Windows user account used on workstations has Full Control, or add the user QuickBooks Database Service (QBDataServiceUser, followed by your QuickBooks version year) with Full Control.
  3. Apply the change and share the folder so network users have read and write access.
  4. Reopen the file from a workstation using the UNC path, for example by typing the host name and shared folder directly rather than a mapped drive letter.

4. Check firewall and antivirus interference

  1. Temporarily disable the firewall or antivirus on the host and try opening the file from a workstation.
  2. If the file opens, re-enable the security software and add exceptions for the QuickBooks program folder and the ports QuickBooks Database Manager uses.
  3. Reboot the host and confirm the file still opens in multi-user mode.

5. Restore from a backup if the file itself is damaged

  1. If File Doctor reports damage it cannot repair, locate your most recent backup, either a local backup (.QBB) or an automatic backup.
  2. Restore the backup to a new folder, not over the damaged file.
  3. Verify the restored file opens cleanly, then re-enter any transactions recorded after the backup was made.
  4. Keep the damaged file set aside until you confirm the restored file is complete.

How to prevent it recurring

  • Host the company file on a wired network connection rather than Wi-Fi where possible; most -6143 0 events our engineers see follow a wireless drop mid-session
  • Set an automatic backup schedule so a restore point always exists within the last day or two
  • Open the file through QuickBooks or a UNC path rather than double-clicking on a mapped or cloud-synced drive
  • Run the QuickBooks Database Server Manager scan on the host after any QuickBooks update
  • Ensure the host computer stays powered on and does not sleep while others are working in the file
  • Exclude the company file folder from aggressive real-time antivirus scanning of database files
Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.