QuickBooks Error 6073-0: The Company File Is Locked Elsewhere

QuickBooks Desktop error 6073-0 blocks you from opening your company file; this guide explains what holds the lock and walks you through clearing it.

Error 6073-0 appears the moment you try to open a company file. QuickBooks finds the file, then refuses to open it because something else already holds a lock on it, or because the folder denies access. The error looks alarming, but it rarely points to damage. In most cases a lock or a permission stands in the way, and clearing it takes minutes.

The exact message

Wording varies slightly between releases, but the message reads, in the form most installs show:

"We're sorry. QuickBooks encountered a problem and we see the error: (-6073, -0). QuickBooks is unable to open this company file. It may be open in another program or in use by another user."

Some installations show only the last two sentences. The number pair stays the same either way, and so does the cause behind it.

What does 6073-0 mean?

This code sits in the 6000 family, which covers failures to open or connect to a company file. The zero is a companion status code and rarely changes the diagnosis. What 6073 says is specific: QuickBooks located the file and began opening it, then lost the race for the file handle. Another program, another session, or a permission setting got there first.

The file itself is usually intact. The path to it is what needs attention.

What triggers it?

Our engineers see five triggers, listed here roughly in order of frequency:

  • The file is open on another computer in single-user mode. Single-user mode requests an exclusive lock, so no second copy of QuickBooks can join.
  • The same user is signed in twice. A disconnected remote session, or one that timed out instead of logging off, holds the file open invisibly.
  • Another program has the file. A backup job, an antivirus scan, or a cloud sync client can lock the file while it copies.
  • Folder permissions block access. The QuickBooks database service needs full rights to the folder holding the file.
  • A stale network descriptor file sends QuickBooks to the wrong host, where the lock check fails.

How do you clear 6073-0?

Work through the scenarios in order. The first one resolves most cases we see.

The file is open elsewhere in single-user mode

  1. Ask everyone who works in the file to close QuickBooks, including anyone working remotely that day.
  2. Check the system tray on each machine. A closed window can leave the program running, so right-click the tray icon and choose Exit.
  3. On the computer that stores the file, open it locally. Choose File, then Switch to Multi-user Mode, then close it again.
  4. Reopen the file from your own workstation. It should now admit you along with everyone else.

A forgotten session still holds the file

  1. On the computer hosting remote sessions, open Task Manager and select the Users tab.
  2. Look for a session marked Disconnected, and sign that session out rather than reconnecting to it.
  3. If you cannot tell which session holds the file, restart the hosting computer. A restart releases every handle, which is blunt but certain.
  4. Try the company file again once the machine is back up.

Another program has locked the file

  1. Close anything that reads the file: Excel after an export, report writers, third-party integrations.
  2. Pause any cloud sync client watching the folder. If the company file lives inside a synced folder, move it to a plain network share, because sync clients lock files mid-upload.
  3. Add the folder holding the company file to your antivirus exclusions, and schedule backup jobs for hours when nobody works in the file.

Folder permissions block access

  1. On the server, right-click the folder that holds the company file and choose Properties, then Sharing.
  2. Confirm every QuickBooks user has read and write access at the share level.
  3. Open the Security tab, grant those same accounts Full control, and apply the change to child objects.
  4. Reconnect to the share from each workstation, then open the file again.

A stale descriptor file

  1. Close QuickBooks on every machine.
  2. In the company file folder, find the file sharing your company file's name but ending in .nd, and rename it by adding .old to the end.
  3. Open the QuickBooks Database Server Manager on the server and scan the folder. The scan writes a fresh descriptor.
  4. Open the company file again.

Can you stop 6073-0 from returning?

Yes, and the habits are simple. Store the company file in a dedicated shared folder that no sync client touches. Make multi-user mode the norm when several people share one file. Ask remote users to sign out of sessions rather than disconnect from them. Exclude the QuickBooks data folder from scans, run backups after hours, and rescan the folder in the Database Server Manager after any server change or file move.

If every scenario above fails, and the error appears while nobody else has the file open, the file itself deserves closer inspection. That inspection is work our engineers perform directly on a copy, so nobody loses a day of bookkeeping while the cause is pinned down.

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.