Cannot open anymore databases - Access database

Question

I am using Office 365 and running Windows 10 pro Version 10.0.19043 Build 19043. My processor is: AMD Ryzen 9 5900X 12-Core Processor, 3701 Mhz, 12 Core(s), 24 Logical Processor(s).

This morning I used an Access database application that I use every morning but got the following message:

Cannot open anymore databases

There have been no changes to the database for sometime and up until this morning it worked fine.

When trying to compact and repair the database I get the following message:

You attempted to open a database already open by user Admin on machine ....

I have restarted the machine and tried repairing Office 365 both to no avail.

When right clicking MS Access on the taskbar and selecting the database I had to do it several times this morning before the database opened. I am wondering if in someway this has screwed the system up.

I also notice that the lock files are trying to synch (with OneDrive?) and cannot be deleted - I get the message below:

Can anyone shed any light on how to solve the problem?

Many thanks.

Answer 1

Hi all,

According to the description this issue was applied after the latest update of Access to version Version 2201 (Build 14827.20158). Microsoft is aware of the bug and currently working on a fix. Please refer to this article for the information and a workaround Access is unable to close and leaves lockfile active (microsoft.com)

In case you want to revert to a previous version you can find the detailed steps here How to revert to an earlier version of Office (microsoft.com)

Sorry for the inconvenience.

Best Regards,

Igor

Answer 2

Some are saying it's fixed with updates. Adding the Desktop to the Trusted Locations fixed it for me.

Answer 3

It was fixed Feb 8. Setting trusted locations for the subfolders fixed some of the issues for me before Microsoft came out with on Feb 8 update, but that update fixed all of my issues, and it has been working flawlessly. I highly recommend you upgrade to the Feb 8 release.

Answer 4

Hi All,

we are having multiple clients experiencing these same errors with the Enterprise build Version 2102 (Build 13801.21214)

I am not having the errors with my building Version 2102 (Build 13801.21156)

Do you have any idea on what could be the reason for this?

Thank you and kind regards

Andrea