On 12/14/2021, SemiAnnual Enterprise channel updated to version 16.0.13801.21086. This is causing several strange behaviors in Microsoft Access. For example: Create a new Access database on a network drive or open an existing database from a network drive. Close it. The .laccdb file is not automatically deleted (even though no other users are in it). Use DAO to OpenDatabase for shared (non-exclusive) access. Error 3050 (“Could not lock file.”) is thrown and the database is not opened. Databases opened on a network drive appear to always be opened for exclusive access. Once one person has opened a database, others can't--even when opening for shared access. Reverting to the prior version 16.0.13801.21050 fixes the problem. This problem seems specific to databases located on a network share. For databases on a local machine, there is no issue.

We have found the culprit for our problem! My team have found that the problem was in security update for MS office 2016 (KB5002099) After uninstall problem is solved

I reported it to Microsoft earlier this morning, waiting to hear back. Use the application feedback command within Access to send in your comments to the Dev Team. I now see another similar thread in this forum with similar symptoms https://answers.microsoft.com/en-us/msoffice/forum/all/this-file-is-in-use-error-received-with-build/4a406c85-6d06-4601-905c-12aa9930d343

Lock File Problems with Access 16.0.13801.21086

Anonymous

On 12/14/2021, SemiAnnual Enterprise channel updated to version 16.0.13801.21086. This is causing several strange behaviors in Microsoft Access. For example:

Create a new Access database on a network drive or open an existing database from a network drive. Close it. The .laccdb file is not automatically deleted (even though no other users are in it).
Use DAO to OpenDatabase for shared (non-exclusive) access. Error 3050 (“Could not lock file.”) is thrown and the database is not opened.
Databases opened on a network drive appear to always be opened for exclusive access. Once one person has opened a database, others can't--even when opening for shared access.

Reverting to the prior version 16.0.13801.21050 fixes the problem.

This problem seems specific to databases located on a network share. For databases on a local machine, there is no issue.

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

98 answers

Anonymous

2021-12-15T11:21:29+00:00

We have found the culprit for our problem!
My team have found that the problem was in security update for MS office 2016 (KB5002099)

After uninstall problem is solved
Was this answer helpful?

5 people found this answer helpful.

0 comments No comments
Anonymous

2021-12-14T18:36:30+00:00

I reported it to Microsoft earlier this morning, waiting to hear back.

Use the application feedback command within Access to send in your comments to the Dev Team.

I now see another similar thread in this forum with similar symptoms

https://answers.microsoft.com/en-us/msoffice/forum/all/this-file-is-in-use-error-received-with-build/4a406c85-6d06-4601-905c-12aa9930d343
Was this answer helpful?

4 people found this answer helpful.

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more