Access Database is getting corrupt again and again

My prior post probably got lost or overlooked.

I moved my Access backend database to a different network folder then relinked the backend tables to the FE db. I have the Compact/Repair on Close option set. We have about 25 - 50 people accessing this database daily. Since I did this change over 3 weeks ago, there have been no more data corruption issues.

I tried to get IT Support to install the Disable Leasing fix on the Host server, but they haven't been responsive. So I came up with this above last ditch option when our database was corrupting multiple times daily, and I had to do something !

I would at least give this option a try if your IT Support group is as unresponsive as mine or the Disable Leasing fix isn't working. It was a lifesaver for me.

George

Here is what I posted two months in a reply to Shane Groff from Microsoft on this forum on this topic. I did not get a reply. I also posted this once or twice previously to everyone and got no replies from anyone who might have tried it. Pretty simple and worth a try.

1. Create a folder on the server and place the uncorrupted database in that folder.
2. Share the folder on the server and give it a share name (e.g., MyDB)
3. Start Powershell as Admin on the server.
4. Set the leasing mode for the new share to None with the following commands:

    set-smbshare MyDB -LeasingMode None

    get-smbshare MyDB | Format-List -Property *    (make sure Leasing Mode is set to None)

5. Restart the server or do NET STOP SERVER then NET START SERVER.
6. Make sure ALL the client PCs open the database file or point to it in a front-end database using the UNC path for the new share name. If they don't use the right share name, disable leasing will still be on.

Note: To turn leasing back on if needed (in case of problems):

    set-smbshare MyDB -LeasingMode Full     (then restart the server or do NET STOP SERVER then NET START SERVER)

To repeat, THIS NEEDS TO BE FIXED BY MICROSOFT. None of the workarounds, including this one and the client based one, are acceptable as a permanent condition of using Microsoft Access on a network. Just unacceptable. IT IS GOING ON TWO YEARS!!! This is a flaw in the Microsoft Networking SMB protocol that needs to be resolved.

Thanks for the reply. Please if possible share the change

NAS devices are no magic pill, and not all created equal either.

I been called into companies where performance was dismal and the solution was to move it off of their NAS and suddenly everything was fine.

That said, I also do have clients running their database on a NAS  without issue.

The real solution here is to not use Windows 10 since it is it that is there for cause of this issue.

I also urge all of you to post on access.uservoice.com and through the feedback command with Access itself.  People need to make noise if they ever want this fixed.

Thank you! I too have been puzzled. What I suggested would disable leasing on one share limiting any performance or other impact dramatically and make it more palatable to customers and server administrators. I don’t have control of my clients servers so I can’t tell you for sure that it will work, but it should from what I understand. I made the client registry change part of our setup and that seems to be working. Some customers made the global disable leasing change on the server and reported that it worked. I suggested the change to just  one share to a few, but I do not have definitive evidence that they made the change and that it fixed the problem.

It seems like this would be a huge step forward if this approach works, at least as an interim step. The root cause still needs to be found and fixed by Microsoft. I hope they do not give up on this. I tried recreating it with a simple database doing repetitive queries, but was unable to. If anyone can do this and give it to Microsoft to help finally resolve this issue, they would be a hero and many of us would be very grateful. I do not like making the client change as I do not know the full performance impact of that change.

I can repost the share-specific change when I get to my office if that helps.