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-11-15T06:16:59+00:00

    Shane,

    The DisableLeasing registry key solved the "unrecognized database" problem for our customers, but it created one nearly as bad: a huge performance hit.

    Our largest customer has about 9 Windows 10 workstations and a Windows 2012 server. Each client has an accde linked to a shared access DB (also an accde) on the server. They are running Access 2013 runtime on each workstation.

    They were getting the "unrecognized database" error frequently, some days every five minutes or so until we applied the DisableLeasing workaround.

    Performance was fine (more or less) until we applied the workaround, then it took a nosedive, and nothing we've done to date has improved it. It's so slow at times that we're probably about to lose them as a customer since we haven't been able to resolve it for them, and it's been several months.

    Our other customers are experiencing the same performance hit even with fewer clients. They were also getting the unrecognized database error until we did the DisableLeasing, which slowed things down to nearly a crawl.

    We need help, or we'll be out of business soon. Or at least out of the Access development business.

    Marty Grant

    Access Developer

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-11-15T05:46:59+00:00

    Hi Shane,

    I've done the inconsistent state workaround a few times and the bug appears again. The interval varies, but the inconsistent state or unrecognized database format error always resurfaces.  I will work with our IT guy to try an implement the enable and disable SMB workaround. The backend is running on a file server and the front-end is in the accde format, so he was not sure how applicable this would be to our scenario. Thanks for replying.

    Chris

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-11-15T05:41:07+00:00

    Shane, I find it almost unbelievable that you aren't able to reproduce this. This issue has been causing many people major issues for many months and and all you have to report is that you can't reproduce the issue? Hard to believe to be honest.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-11-15T05:30:28+00:00

    Hi Chris,

    There isn't anything new for this.

    I don't see immediately in this thread, but have you tried the suggested workaround to set the DisableLeasing registry key?

    We still have not been able to reproduce the issue in a controlled setting, but are investigating some different possibilities.

    Shane Groff

    Access Engineering

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-11-15T05:04:01+00:00

    Daniel, do you think the 1809 release this week will contain a fix for this issue?  There's one machine that is crashing a database every couple of days.  This never happened until some time after the 1803 update.

    Was this answer helpful?

    0 comments