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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-06-01T23:08:32+00:00

    The appears to be some issue as there have been several recent posts relating to sudden issues with databases that previously ran fine.

    Since you believe it is a recent update that is causing the issue (and it' tend to agree) have you tried reverting your installation to a previously problem free build?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-04-29T17:38:14+00:00

    We had about 36 queries, many update, delete and append queries. When it seemed to be a particular query we would test by having the process skip that query, it then just became corrupted on the next query.  

    SO, we divided the queries into three sets, A, B and C. 

    We tested and found that regardless of the order executed, either A-B-C or A-C-B or B-A-C or B-C-A or C-A-B or C-B-A

    the corruption would always take place in the second set. It seemed that it was not the specific query that was the issue, but some issue which involved an accumulation affect, (maybe in some communication/network buffer?)

    Now this corruption would only work when there were at least two in the database thru the network. (Though there were certain conditions when the corruption would not take place depending primarily on whether the one running the queries was the first one in the database.)

    In any case, instead of using the workarounds, we worked it out so those processes would only be initiated with one person logged in, since it was just needed once in the morning.  This took care of 95% of the corruption issue; there would still be an issue once or twice a month.

    NOW, for the past 5 months we have had no corruptions.  So, to test it, we allowed for the series of queries to be run with others logged in as well, and there is no longer a corruption issue.  (I assume there has been some Microsoft update, may be relating to networking, that inadvertantly has also corrected the corruption issue.)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2019-01-24T17:26:42+00:00

    Has anyone employed the workstation registry hack provided here by ITYIPMan and found it to work without combining it with the DisableLeasing workaround on the server?

    https://github.com/MicrosoftDocs/windows-itpro-docs/issues/934

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-06-19T07:54:38+00:00

    Hi Shane,

    after almost a week later I can confirm we haven't had the issue anymore on the database.

    However, as I mentioned before I only applied the regkey (DisableLeasing) on the server where the database is on.

    I will keep it this way until I see something in the release notes of a windows update.

    thanks!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-06-05T16:47:32+00:00

    Did you try rolling back recent updates?

    Are all your users all running the same version of Access?  Which one?

    Is your database properly split and each user given their own local copy of the front-end?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments