This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted. We ran compact and repair. But it still getting corrupted again and again. This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.
Is there anything i have check in new windows update or any other step to prevent database corruption?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
No, it's not limited to older databases as I have clients with dbs created in A2013 and running with O365 that have exhibited this error.
I've been wondering if this problem is limited to older versions of databases. The one we have trouble with was created back in 2002 and nobody can even remember who created it originally. I told my manager that it was probably time to rebuild that thing. Fortunately, it is not a huge database. The "corruption" does appear when they try to add a record and save it. Just opening and viewing does not produce the problem.
I did not restart the server after applying the Disable Leasing fix. Maybe that had to be done to prevent the whole mess. However, the Microsoft documentation does not say to do so. They just say to restart the SERVER service.
Thanks for the confirmation Daniel. Sounds like it could be the luck of the draw to some extent. I'm going to confirm with the IT guy who applied the fix at one current client whether he had the drive mapping issues, just out of interest.
I have databases scattered all over the place, some as old as 10 years. I know that some of these are still in use but I've heard of no problems with these. These are with large companies who are generally slow to update Windows versions but I think they would surely be on 1803 or later. What I don't understand is why they have experienced no problems. Perhaps they are running the databases in a remote desktop environment, which I'm assuming gets rid of the problem when frontend and backend are on the same server.
Is the issue much more likely to occur when delete and append queries are run on a regular basis? That's the impression I got reading through earlier posts in this thread.
I can confirm that it isn't always smooth sailing.
I've applied the fix at a couple clients where everything was seamless.
I also applied it at one client and then all their mapped drives no longer worked and had to be recreated.
In all cases, the disableleasing registry fix, as suggested by Microsoft, resolved the unrecognized database error.