Quick answer
A QuickBooks file in use error means another session holds a lock on the company file. Sometimes the lock is genuine: another user is running a task that only one person can perform. Just as often it is stale — a crashed QBW32.exe process, a second computer hosting multi-user access, or an .ND file that still reports the file as open. Confirm who is actually in the file before you clear anything.
What the file in use message actually means
QuickBooks Desktop uses two different locking systems, and the wording on screen tells you which one fired.
Real concurrency locks protect tasks that only one user can run at a time. Payroll, bank feeds, and certain transaction edits are locked for everyone else even in multi-user mode. The dialog usually names the user or the task, and the lock releases when that user finishes.
Stale locks behave differently. QuickBooks releases its claim on the company file when a user signs out normally. If QuickBooks crashed, was ended in Task Manager, or lost its network connection, the file can stay marked "in use" with nobody working in it. An orphaned process or an old .ND file (the 1 KB network data file that helps QuickBooks detect whether a company file is in use) keeps the block alive.
| Message you see | What it usually is | Start with |
|---|---|---|
| Company File in use. Please wait. Only one user at a time is allowed to do (a task). | A real one-at-a-time task is running for another user | Wait, then Step 1 |
| Another QuickBooks user is currently performing a task which must finish before you can continue. | Genuine concurrency lock | Ask the named user to finish |
| Sorry, you cannot change this (transaction) now. (Another user) is currently doing a task that uses it. | Transaction-level lock held by another session | Step 1 |
| The same user is named every time, but that person is not in QuickBooks | A stale user session inside the company file | Steps 2 and 3 |
| Waiting for company file, or the error appears on several workstations | Hosting conflict or a performance problem | Step 4 |
Common causes, ranked by how often technicians see them
- A stuck background process.
QBW32.exe,QBDBMgrN.exe, orQBCFMonitorService.exesurvives a crash or a forced close and keeps the file handle open. This is the most common reason a lock will not clear on its own. - More than one computer hosting multi-user access. When a workstation also hosts the file, connections and locks collide. Only the server should host.
- A stale user session inside the company file. QuickBooks still lists the user as signed in because that workstation never closed the file cleanly.
- A damaged, missing, or outdated
.NDfile. After a file move or a version upgrade, the.NDcan point at the wrong server, port, or path. - Read-only conditions. The
.QBWis marked read-only, folder permissions lost Modify rights, or the file sits in a OneDrive, Dropbox, or Google Drive folder where a sync client toggles locks. - Hosted or second-session leftovers. A disconnected hosted desktop session, or a second company file window, never released the file.
Before you clear the lock
Back up first, and confirm nobody is working. Ending a QuickBooks process can discard a transaction that has not been saved yet. Copy the entire company-file folder — the .QBW, .ND, .TLG, and .DSN files together — to another drive before you start. Plan on 15 to 30 minutes.
- Confirm no one has a task running by phone or chat, not by guessing from the error alone.
- Note whether the message names a user. That single detail decides which step below matters most.
- Confirm whether the file is in single-user or multi-user mode. The File menu shows Switch to Single-user Mode or Switch to Multi-user Mode.
- Know where your last clean backup is stored before you end any process.
How to clear a stuck QuickBooks file lock
Confirm who really holds the file
On a second workstation, open QuickBooks, go to the Company menu, select Users, then View Users. A genuine lock shows a signed-in user; that user's screen shows the task in progress. Press F2 (or Ctrl + 1) and review the Local Server Information section of the Product Information window to see which computer is serving the file.
Have the named user sign out and back in
Ask that person to close QuickBooks, sign out of the company file, reopen it, and sign in again. Then check View Users once more. If the user no longer appears as signed in, retry the task that failed. If the name stays on the list, the session is stale — continue to the next step.
End the stuck QuickBooks processes
On each computer where QuickBooks is already closed, open Task Manager with Ctrl + Shift + Esc, go to the Details tab, and end any of these you find: QBW32.exe, QBDBMgr.exe, QBDBMgrN.exe, QBCFMonitorService.exe, and QBUpdate.exe.
Never end QBW32.exe while someone has an unsaved transaction on screen. QuickBooks can recover an interrupted session from the transaction log on the next open, but the entry being typed at that moment may be lost.
Make sure only the server hosts multi-user access
On every computer except the file server, open QuickBooks, go to File → Utilities, and select Stop Hosting Multi-User Access if it appears. Then, on the server, press Windows + R, type services.msc, and restart the QuickBooksDBXX service.
Restarting the service disconnects every user, so pick a quiet moment. Have everyone sign back in afterward and test the task again.
Version note. Intuit's numbering maps QuickBooksDB30 to QuickBooks 2020, so newer releases use higher numbers. Confirm the exact service name in services.msc rather than assuming.
Rename the .ND support file and rescan
With every user signed out, find the file that matches your company file name with an .nd extension — company.qbw.nd or company.nd. Rename it by adding .old to the end, then open the company file again or rescan the folder with QuickBooks Database Server Manager. The .ND file is a small text configuration file, and QuickBooks recreates it within seconds.
Remove read-only conditions on the file and folder
Right-click the .QBW file, choose Properties, clear the Read-only checkbox on the General tab, then open Advanced and clear Compress and Encrypt. Right-click the folder, open Properties → Security, and confirm your Windows account has Modify or Full control.
If the file lives in a cloud-sync folder, move it to a plain local or server folder. Sync clients lock files intermittently, which produces "in use" errors that come and go with no pattern.
Clear hosted and second-session locks
In a hosted QuickBooks environment, sign out of QuickBooks inside the hosted desktop and close that session properly instead of only closing the browser or RDP window. If a dropped connection left a session behind, ask your hosting provider to end it — no local step can release a session that lives on their server.
If you work with two company files at once, only QuickBooks Accountant and QuickBooks Desktop Enterprise support it, and the second file must be opened with File → Open Second Company. Do not use Open or Restore Company for the second file; that path is for switching files, not running two at once.
Verify the lock is cleared
- Open the company file as a standard user, not as administrator, and press F2 to confirm the file and server information.
- Check Company → Users → View Users and confirm only the people actually working are signed in.
- From a second workstation, post a test invoice and then delete it, or run a small report that previously triggered the message.
- Close QuickBooks cleanly, reopen it, and confirm the message does not return on the first open of the day.
If the file in use message keeps coming back
Recurring locks almost always trace back to one of four things: a cloud-sync folder, more than one hosting computer, a stale user record that reappears, or an underlying company-file problem. If the lock arrives alongside other errors — especially the error 6000 family — treat it as a data integrity issue and work through the data damage recovery order instead of clearing the lock again.
Two host computers on one network are easier to miss than they sound. Recheck File → Utilities on every machine after a version upgrade or a new PC is added. If the .ND files keep going stale, review the service configuration with the Database Server Manager workflow, and if the file itself keeps failing, professional company-file repair or Intuit support is the right escalation.
Prevention
- Teach users to exit QuickBooks normally. A clean sign-out releases the lock immediately, while a Task Manager kill leaves cleanup behind.
- Host multi-user access on one computer only. After adding workstations, verify hosting is off everywhere else.
- Keep company files on local drives or a properly shared server folder, never in a consumer sync folder.
- Restart the server and database service on a schedule. Long uptimes and dropped connections breed orphaned sessions.
- Review the multi-user hosting checklist whenever the network changes, and run Verify Data twice a year.
- Test a backup restore at least once a quarter so a real lock emergency never becomes a data emergency.
Frequently asked questions
Is it safe to rename or delete the .QBW.ND file?
Yes, when everyone is signed out. The .ND file is a roughly 1 KB configuration file that tells QuickBooks where the database server is and whether the company file is in use. Your transactions live in the .QBW file. Rename the .ND file and QuickBooks or Database Server Manager recreates it automatically.
Can ending QBW32.exe corrupt my company file?
Ending the process rarely damages the file — QuickBooks uses the transaction log to recover the last session — but any transaction still open on screen can be lost. Always back up the company-file folder first, and use Task Manager only after QuickBooks is otherwise closed.
Why does QuickBooks still say a user is signed in after they closed QuickBooks?
That is a stale session. Their workstation did not release the file cleanly, so the company file still lists them as active. Have them reopen and sign out of QuickBooks properly, then check View Users. If the name will not clear, end the leftover processes and rename the .ND file.
Can two people use the same QuickBooks company file at the same time?
Yes, in multi-user mode with enough user licenses — except for tasks that QuickBooks limits to one user at a time, such as payroll and bank feeds. If everyone is forced into single-user behavior, check that only one computer hosts multi-user access.
Does a file in use error mean my data is damaged?
Usually not. The message means a lock exists, not that the file is corrupt. If the lock clears but other errors appear, or if the file fails to open afterward, run File → Utilities → Verify Data to check file integrity before trying anything more aggressive.