QuickBooks Error 6073, 0
Let’s Dive in to see…
How to Fix QuickBooks Error=6073, 0
QuickBooks Company File Error · 6073, 0 · Read/Write Failure
How to Fix QuickBooks Error 6073, 0
QuickBooks displays: "We're sorry. QuickBooks could not open the company file. Error code: -6073, 0"
Error 6073, 0 is a company file read/write access failure with an unspecified OS error. At QuickFix Bookkeeping, the 0 secondary code distinguishes this from 6073, -816 (which has an explicit lock component): 6073, 0 means the OS returned a generic access error — QB couldn't open the file but there's no recognised exclusive lock on it. Common causes include file attribute issues, permission problems, or QB components failing to initialise file access.
6073, 0 vs 6073, -816 — The Sub-Code Distinction
6073, 0 — this page
Unspecified OS access error — no recognised lock. QB failed to open the file but couldn't classify the Windows error further. Fix: check permissions, Read-Only attribute, restart QBDSM, rename .ND.
6073, -816
Explicit exclusive lock — another process or session has the file exclusively locked. -816 always means a lock. Fix: find and clear the lock (stale .lock file, backup software, lingering QB process).
What Causes QuickBooks Error 6073, 0?
Read-Only Attribute on Company File
Common 6073, 0 cause — the .QBW file has its Read-Only attribute set. QB needs write access to open a company file — a Read-Only file can't be opened in QB. Windows returns a generic access error (mapped to the 0 sub-code). Right-click .QBW → Properties → uncheck Read-only → Apply.
Missing Write Permissions
The Windows user or QBDataServiceUser[XX] account doesn't have write permissions on the company file folder. QB's file open requires both read and write access — a read-only permission grants access but QB's file-locking mechanism fails with a generic error. Add Full Control for both accounts.
QBDSM Not Running in Multi-User
In multi-user mode, QBDSM on the host must be running and must have scanned the company file folder. When QBDSM isn't functioning, QB receives a generic OS error when it tries to establish the file access channel — reported as 6073, 0. Restart QuickBooksDB service and run QBDSM rescan.
AV Blocking File Access at Open
An AV product intercepting QB's file open request produces a generic access denied error that Windows returns as the 0 sub-code. Temporarily disabling AV and retrying confirms this cause. Add the company file folder and QB executables to AV exclusions.
Corrupted .ND File
A corrupted .ND file causes QBDSM to return incorrect connection data to QB when it tries to open the file. QB gets an unexpected response from its own infrastructure and reports a generic access error (0 sub-code). Renaming the .ND and rescanning forces a clean rebuild.
Disk or File System Error
Bad sectors or file system corruption on the drive hosting the company file cause Windows to return an unspecified error when QB tries to open the file. Running chkdsk /f on the drive and then retrying reveals if the disk is the root cause.
How to Fix QuickBooks Error 6073, 0
Related QuickBooks Errors
Error 6073, 0 Persisting After Permissions Fix and .ND Rename?
Let QuickFix Bookkeeping Identify the Access Block.
Persistent 6073, 0 after permissions and .ND fixes usually means a hidden Deny ACE or EFS encryption is producing the generic access error — we audit the full ACL and resolve the specific block.
Book a Free 30-Minute ConsultationNo obligation. Same-day response.