Microsoft Access: Database is in an inconsistent state on Network Shares

Question

We have a split .accdb database stored on a shared network drive. Since the latest Office update, users are constantly getting the error 'Microsoft Access has detected that this database is in an inconsistent state.'

Running 'Compact and Repair' dozens of times, but the error returns within an hour

Answer 1

Hi,

The AI already mentioned the bad old Monster Bug and that disabling Leasing is the workaround for it. The problem has never really been fixed but happens rarely in recent years, most probably because of changes in Windows 11. You can read more about it in this old Microsoft support article.

It would be interesting to know if you are one of the rare victims nowadays or if it is a different new problem with similar symptoms. In the latter case you could try to roll back to a previous Office build.

Servus
Karl

---

Access Forever News DevCon
Access-Entwickler-Konferenz AEK

Answer 2

Hi Nichols Dylan

Thank you for reaching out to the Microsoft Q&A Forum and sharing your issue.

To better understand the situation, could you please help confirm a few points:

• Which version of Microsoft Access you are using (for example, Microsoft 365 Apps, Access 2019, Access 2021)?
• The exact Office version and build, and whether the issue started right after a specific Office update?

As a first step, I recommend reviewing the suggestions provided in the Q&A Assist response below and considering testing the proposed workaround to see if it improves the behavior.

If the issue still occurs after that, you may also try creating a new blank database and importing the tables and objects from the existing back‑end. This can help rule out any underlying corruption that may not be resolved by running Compact and Repair repeatedly.

Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution.  

I look forward to your update.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

The behavior matches a known issue with Access databases on network file shares that became common after certain Windows and Office updates, especially with split databases used by multiple users.

For a split database on a network share, apply the supported workaround on the file server that hosts the back-end .accdb:

1. On the server that stores the back-end database, sign in with an account that has local administrator rights.
2. Open an elevated Command Prompt:
   • Select Windows Start, type Command.
   • Right‑click Command Prompt and choose Run as administrator.
3. Run these commands exactly as shown to disable SMB leasing for the server service:

      REG ADD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters /v DisableLeasing /t REG_DWORD /d 1 /f
      NET STOP SERVER
      NET START SERVER
   

   This change is required only on the machine hosting the shared back-end database, not on each client.
4. Ensure all client machines running Access are fully updated to the latest Office build, as the fix for related network‑share issues may not be applied automatically. Follow the steps in Install Office updates on every machine that uses Access.

Additional points:

• The error is triggered by specific usage patterns of the Access Database Engine with networked files and simultaneous multi‑user access; disabling leasing on the server mitigates this.
• Continuing to use the database in this state can increase the risk of corruption. Maintain regular backups and continue to use Compact and Repair as needed, but rely on the server‑side leasing workaround and Office updates to address the root cause.

---

References:

• Access reports that databases are in an 'inconsistent state'
• Error in Access when opening a database on a network file share
• Compact and repair a database