Recent rash of Microsoft Access database files in an inconsistent state

It has recently been reported several times. A very thorough coverage of this issue can be found here.

Strangely, the cure can - at least for some cases - be found in old support threads:

Moved to Server 2012 getting Access Database Corruption

Cannot access shared files or folders on a drive in Windows Server 2012 or Windows Server 2012 R2

Comments:

It’s a bit strange though as the patch to fix the issue is back in May 2014 which is already installed on the server.

I can only think that something in the latest Windows 10 Build 1803 has brought up the issue again as it was PC’s that are running that build were causing the problem.

The fix is adding the following entry into Vospers Server 2012 R2 registry:

Key:   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Value: DisableLeasing
Type:  DWORD
Data:  0x1

We testing this on our server and the problem went away. As soon as we changed the ‘Disable leasing’ value to ‘0’ again, the problem returned.

I can’t find a reasonable explanation yet as to why this has started to happen last week but if it works and doesn’t cause any further issues elsewhere then I’m ok with that.