Access Database is getting corrupt again and again

First and foremost, after a discussion yesterday i found out that the wording on the workaround page was incorrect.  The registry Jack workaround only needs to be applied to the back-end server.  It does NOT need to be applied to each individual user's PC. (Would have been nice to know that for the past year!)

The registry hack can be found on Microsoft's page on the subject,https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state--7ec975da-f7a9-4414-a306-d3a7c422dc1d?ui=en-US&rs=en-US&ad=US, and yes you could create a reg file to deploy it instead of running it directly in the command prompt.

Lastly, as reported above by others, when i applied the fix, i lost all the mapped drives.  Fun times were had by all.

I applied the registry "FIX" to about 6 Windows 10 workstations.  1/2 the group had the access db corruption problem, the other 1/2 didn't.  I only applied the fix to the workstations that needed it.  We have had no problems with network connectivity or network drive mappings as a result of the "FIX".  

I did not apply the registry hack to the server that the database lives on - only client machines.  That might be what messed things up for you?  I could easily see messing with network settings on a file server causing major problems.

 am not sure why the Disable Leasing fix to the server is still being mentioned as a possible solution.

I tried the Disable Leasing Fix because it is still Microsoft's official suggested workaround. When that fix messed things up I removed the registry entry, rebooted the server and things went back to normal. Then I applied this fix:

"FileInfoCacheLifetime"=dword:00000000

"FileNotFoundCacheLifetime"=dword:00000000

"DirectoryCacheLifetime"=dword:00000000

So far users have been in there for an hour and haven't heard complaints.

I'm wondering if we had the back end hosted on Server 2019 and with all workstations being Windows 10 if we would see this issue. Do you guys think it's OS incompatibility with different versions in the mix or is it just Access?

I applied the registry "FIX" to about 6 Windows 10 workstations.  1/2 the group had the access db corruption problem, the other 1/2 didn't.  I only applied the fix to the workstations that needed it.  We have had no problems with network connectivity or network drive mappings as a result of the "FIX".  

I did not apply the registry hack to the server that the database lives on - only client machines.  That might be what messed things up for you?  I could easily see messing with network settings on a file server causing major problems.  

Are you talking about the Disable Leasing fix or the other one?

Microsoft has just updated their status on this issue and now they are saying it only needs to be applied on the server hosting the back end.

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-%EF%BB%BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d?ui=en-US&rs=en-US&ad=US

However, in my experience doing this, I lost network drives and computers could not contact the domain (the server hosting the back end is also our DC, maybe that's the issue?). All workstations on the network were affected regardless of having the fix applied or not.

First and foremost, after a discussion yesterday i found out that the wording on the workaround page was incorrect.  The registry Jack workaround only needs to be applied to the back-end server.  It does NOT need to be applied to each individual user's PC. (Would have been nice to know that for the past year!)

The registry hack can be found on Microsoft's page on the subject,https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state--7ec975da-f7a9-4414-a306-d3a7c422dc1d?ui=en-US&rs=en-US&ad=US, and yes you could create a reg file to deploy it instead of running it directly in the command prompt.

Lastly, as reported above by others, when i applied the fix, i lost all the mapped drives.  Fun times were had by all.

Daniel, are you in contact with Microsoft by any chance? It's funny that you posted this and their documentation was updated today. Do you happen to know what is Microsoft's stance on the other suggested fix? Do you know what it actually does?

"FileInfoCacheLifetime"=dword:00000000

"FileNotFoundCacheLifetime"=dword:00000000

"DirectoryCacheLifetime"=dword:00000000