Access Database is getting corrupt again and again

Hey Wayne,

I certainly would love to be able to isolate and resolve the issue for those people that are encountering it.  Unfortunately, this problem doesn't occur on the systems we've tested with, and even for the customers who are hitting this, there isn't a clear pattern or set of steps that consistently lead to the error.  There is something in the combination of hardware and software environment, Windows and Access that are interacting in a way that is leading to the problems that people are seeing. 

I'm not going to go into details of our efforts so far, but will certainly let people know (through the Fixes and Workarounds page if I don't get back to here), when we having something better than the current workaround.

Shane Groff

Access Engineering

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

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

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.

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