Access Database is getting corrupt again and again

Anonymous
2018-06-01T17:47:41+00:00

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?

Microsoft 365 and Office | Access | For home | Windows

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.

0 comments

604 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-08-14T21:36:44+00:00

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-14T22:01:08+00:00

    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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-08-14T22:07:16+00:00

    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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-14T23:01:52+00:00

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-08-15T20:30:45+00:00

    Any news if the issue is officialy (my MS) fixed with the KB 4512508 (August 13, 2019) update ?

    i just applied it but I don't have currently access to local network to check it.

    At least, when applied the update, the SMB Registry fix was still there and not changed to previous status.

    So the

    FileInfoCacheLifetime    REG_DWORD    0x0

    FileNotFoundCacheLifetime    REG_DWORD    0x0

    DirectoryCacheLifetime    REG_DWORD    0x0

    were still there ...

    Was this answer helpful?

    0 comments