Why the "sample file" test matters for 6144-304: When you see -6144, -304, try opening a QB sample file (QB → File → Open or Restore Company → Open a Sample File). If the sample file fails with the same error — the QB installation or QBDataServiceUser account is damaged, confirming the fix is on the program side. If the sample file opens correctly but your company file fails — the specific error is with your company file's network/hosting setup rather than a pure 6144-304 installation error; see the 6000 series troubleshooting guide for file-specific fixes. The 6144-304 code most characteristically appears when the sample file itself is the problem.

Damaged QB Installation

Primary cause for sample-file variant — QB's program files are incomplete or corrupted, preventing it from opening even sample company files. The error appears when the QB application itself can't function correctly. Running the Install Diagnostic Tool or repairing the QB installation resolves this. The sample file failing is the diagnostic confirmation.

Damaged QBDataServiceUser Account

From Intuit's sub-code table for 6144: the QBDataServiceUser Windows account (created by QB to manage database services) is damaged or has incorrect permissions. QB's database service can't operate correctly, causing -6144, -304 and related codes. Recreating the account or repairing the QB installation fixes this.

Incorrect or Missing .ND File

When the .ND (Network Data) file associated with the company file is missing, incorrect, or points to a wrong server, QB can't establish the database connection needed to open the file. This particularly affects multi-user setups where the QBDSM can't find or serve the company file correctly. Renaming the .ND + QBDSM rescan rebuilds it.

Corrupted Company File (Non-Sample Variant)

When -6144, -304 appears for a live company file (sample opens fine), the .QBW file has internal damage. System shutdowns during file operations, disk errors, or malware can corrupt the .QBW. File Doctor repairs minor damage; backup restore is needed for severe corruption. Run Verify/Rebuild Data after recovery.

Firewall or Antivirus Blocking QB Services

Security software blocking QB's database service or the QBDataServiceUser account's file access produces -6144, -304 in multi-user environments. The QBCFMonitorService (company file monitor) must also run unimpeded. Check that QB's services are allowed in firewall and antivirus settings.

Incorrect Hosting Configuration

Hosting enabled on a workstation rather than the server, or no machine hosting the file when multi-user mode is needed. QB's database layer fails to find a valid host for the company file and reports -6144, -304. Verify: only the server has "Host Multi-User Access" enabled; all workstations must show "Stop Hosting" as inactive.

METHOD 1 Sample File Test + Repair QB Installation Confirms if it's QB installation damage

METHOD 2 Enable QBCFMonitorService + Fix Hosting + Rename .ND Service account or network configuration

METHOD 3 Run File Doctor + Restore Backup (Sample Opens Fine) Company file damage — not QB installation

METHOD 4 Copy File to Desktop + Create New QB Folder + Check Permissions Folder permissions or damaged shared folder

Why does the error code say "occurs in a sample file" — does that mean I accidentally opened a sample?

No — it means the error code -6144, -304 is the specific code that Intuit's system assigns when the problem manifests in (or is identifiable through) a sample file test. The "Occurs in a sample file" description in Intuit's error table is telling you the diagnostic characteristic of this error code, not that you were using a sample file. In practice, -6144, -304 can appear when trying to open your real company file — but if you then try to open a sample file and get the same error, that confirms QB itself is damaged (not just your company file). If the sample file opens fine, then only your specific company file is affected. This distinction determines the entire repair path.

Is my company data at risk from Error 6144, 304?

In most cases, your accounting data is not at risk. When -6144, -304 occurs because the QB installation is damaged (sample file also fails), your .QBW company file is untouched — the data is fine, but QB can't read it due to the program damage. After repairing QB, the data will be accessible. When -6144, -304 occurs because the company file itself is damaged (sample opens fine but live file fails), there's a risk of data issues — run Verify Data after File Doctor to check integrity and rebuild if needed. Always take a backup before any repair steps as a precaution.