QuickBooks Company File Error - 6xxx Series

How to Fix QuickBooks Error Code 6098

QuickBooks fails to open the company file with: "Error 6098: Another QuickBooks instance is using this company file."

Error 6098 appears when QuickBooks detects that another instance of QuickBooks -- either on the same machine or on another machine on the network -- already has the company file open, or has left a lock file behind from a previous session. At QuickFix Bookkeeping, 6098 is one of the faster 6xxx errors to fix because the cause is almost always a stale lock file, not actual corruption.

The QuickFix Bookkeeping Distinction

Error 6098 is almost always a stale lock file, not a real conflict with another active session.

What it looks like

Another user or machine is actively using the company file and you need to wait. This is the assumption most users make, and it leads them to do nothing for hours while the real problem -- a lock file that was never cleaned up -- persists.

What is actually happening

QuickBooks writes a .ND (network descriptor) and .TLG (transaction log) file alongside every company file. When a session ends abnormally -- power cut, network drop, force-close -- these lock markers are not cleaned up. The next QuickBooks session sees them and reports 6098.

First step: Confirm whether anyone actually has the file open before touching anything. In multi-user mode, check QuickBooks > Company > Users > Who Is Logged In. If nobody is listed, the problem is a stale lock file.

What Is QuickBooks Error 6098?

Error code

6098

6xxx Series - Company File Lock Error

What it means

QuickBooks fails to open the company file with: "Error 6098: Another QuickBooks instance is using this company file."

What Causes This Error?

🔒

Stale Lock File from Previous Session

The most common cause. A previous QuickBooks session ended abnormally (power cut, network drop, force-close) and left behind .ND or .TLG lock markers that were not cleaned up.

🖥️

QuickBooks Still Running in Background

QuickBooks appears closed but a background process is still holding the file open. Task Manager will show QBW32.exe or QBDBMgrN.exe still running.

🌐

Another Workstation Has the File Open

In multi-user mode, another machine on the network genuinely has the company file open. The fix is asking that user to close it, or restarting the QuickBooks Database Server Manager service.

⚙️

QuickBooks Database Server Manager Issue

The QBDBMGR service is in a stuck state -- neither fully open nor fully closed. It holds the file lock without any active user session.

6xxx Error Series

6000

General company file error

6073

File open by another instance

6098

This page -- Another instance is using this file

6123

Connection to company file lost

How to Fix This Error

METHOD 1Close All QuickBooks Processes and Remove Lock FilesMost common fix
1

Open Task Manager (Ctrl+Shift+Esc) and end any running processes named QBW32.exe, QBDBMgrN.exe, or QBUpdate.exe.

2

Navigate to the folder containing your company file (.QBW).

3

Delete or rename the .ND file (e.g. CompanyName.QBW.ND) and the .TLG file if present.

4

Restart QuickBooks and open the company file. QuickBooks recreates the .ND and .TLG files automatically.

METHOD 2Restart QuickBooks Database Server ManagerMulti-user environments
1

On the server machine, open Services (Win+R > services.msc).

2

Find QuickBooksDBXX (where XX is your QB version year, e.g. QB 2024 = QBDB34).

3

Right-click > Restart. Wait for the service to fully restart.

4

Return to the workstation and attempt to open the company file again.

METHOD 3Switch to Single-User Mode and BackPersistent multi-user lock
1

Have all other users close QuickBooks on their machines.

2

On the host machine: File > Switch to Single-User Mode.

3

Close QuickBooks completely on the host machine, then reopen it.

4

File > Switch to Multi-User Mode. Other users can now reconnect.

Related Errors

Error 6098 Persisting After Removing Lock Files?

Let QuickFix Bookkeeping Resolve Your Company File Lock.

Persistent 6098 after removing .ND files usually means the QBDB service has a deeper configuration issue or a Group Policy is preventing the lock file from being deleted. We diagnose and fix remotely in a single session.

Book a Free 30-Minute Consultation

No obligation. Same-day response.