QuickBooks Error -6098, 5 -- Resolving Database Server Hosting Conflicts

Error -6098, 5 blocks multi-user access when the database server finds the file open with incompatible hosting settings; our engineers walk through resolution.

When a QuickBooks Desktop company file is opened in multi-user mode, the QuickBooks Database Server Manager must have exclusive control over how the file is hosted on the server. Error -6098, 5 occurs when that server-side database engine detects a hosting conflict — the file is already locked or open under a hosting configuration that conflicts with the current request. Our engineers have resolved this error across single-machine, peer-to-peer, and dedicated server environments, and the fix is almost always a matter of correcting hosting settings or clearing a stale lock.

What the Error Message Says

The full message typically reads:

Warning: QuickBooks is attempting to open this company file: [path\filename.qbw]. Before you can open the company file on your computer, you must first open the company file on the computer where the company file is located. (-6098, 5)

In some configurations the message appears alongside a secondary prompt about database server restrictions or a recommendation to switch to single-user mode.

What the Code Means

The -6098, 5 code is a compound error. The -6098 component signals that the database server manager cannot grant access to the file because it has been opened or hosted in a way that prevents the requested connection type. The secondary 5 indicates a permission or access-level mismatch at the database engine layer — the server process is running, but it cannot reconcile the file's current hosting state with the incoming request.

What Triggers It

The most common triggers, in order of frequency our engineers see:

1. Hosting is enabled on a workstation instead of only on the server. When a workstation has hosting turned on, it attempts to act as a database server, creating a conflict with the actual server.
2. The .ND (Network Descriptor) file is corrupted or stale. This file tells QuickBooks where the database server is. If it points to the wrong machine or contains outdated entries, the connection fails.
3. A previous QuickBooks session crashed, leaving behind a .tlg (transaction log) lock or a .qbw.nd lock file that prevents a clean reopen.
4. Multiple Database Server Manager instances are running after an upgrade or reinstall, and the older service is holding the file open.
5. Windows folder permissions on the server do not grant full control to the QBDataServiceUser account.

How to Fix It

Scenario 1: Hosting Enabled on a Workstation (Most Common)

1. On every workstation that accesses the file, open QuickBooks and press F2 to open the Product Information window.
2. Look at the Hosting field near the center of the screen. It should read Hosting: Off on all workstations.
3. If any workstation shows Hosting: On, go to File > Utilities. If you see Stop Hosting Multi-User Access, select it. Confirm the change and restart the workstation when prompted.
4. On the server machine, press F2 and confirm it reads Hosting: On. If it does not, go to File > Utilities > Host Multi-User Access and confirm.
5. Open the company file from the server first, then have each workstation open it.

Scenario 2: Corrupted or Stale .ND File

1. Close QuickBooks on all machines.
2. On the server, navigate to the folder containing the company file.
3. Locate the file ending in .ND with the same base name as the company file (for example, CompanyFile.qbw.nd).
4. Right-click the .ND file and rename it to CompanyFile.qbw.nd.OLD.
5. Open the QuickBooks Database Server Manager on the server (Start menu > QuickBooks > QuickBooks Database Server Manager).
6. Click Start Scan and point it at the folder containing the company file. This regenerates a fresh .ND file.
7. After the scan completes, open the company file from the server, then from each workstation.

Scenario 3: Leftover Lock Files After a Crash

1. Close QuickBooks on all machines.
2. On the server, navigate to the company file folder.
3. Look for any .lck files or files with the same base name ending in .tlg.lck. Rename them with a .OLD extension or delete them.
4. Do not delete the .tlg file itself — only .lck lock files.
5. Restart the server, then reopen the company file.

Scenario 4: Multiple Database Server Manager Versions

1. Open Control Panel > Programs and Features on the server.
2. Look for multiple entries of QuickBooks Database Server Manager across different years.
3. Uninstall any versions older than the QuickBooks Desktop version currently in use.
4. Reboot the server.
5. Run the Database Server Manager scan again on the company file folder.

Scenario 5: Windows Folder Permissions

1. On the server, right-click the folder containing the company file and select Properties > Security.
2. Click Edit and ensure the QBDataServiceUser account (the exact name includes the QuickBooks version year) has Full Control.
3. Apply the changes and have each user attempt to open the file again.

How to Prevent It Recurring

Our engineers recommend standardizing on a dedicated server or hosting machine as the single point of entry for the company file. After any QuickBooks update or upgrade, run the Database Server Manager scan before users reconnect. Avoid opening the company file directly from a mapped drive letter if a UNC path (\\ServerName\ShareName) is available, as mapped drives can reconnect with different credentials after a reboot and trigger hosting mismatches. Finally, if a workstation crashes while QuickBooks is open, have that user wait sixty seconds before attempting to reopen the file — the database engine needs time to release its locks cleanly.