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.

Hello Shane, I have had Version 2108, Build 14326.20738 installed for a few weeks and everything has been working fine. No file locking issues. I just got an update notice from my Software Center that is wants to install Version 2108, Build 14326. 20784 Looks like this was released on Feb 8, according to this: https://docs.microsoft.com/en-us/officeupdates/microsoft365-apps-security-updates I've seen posts on other pages that the file locking issue may have returned for some people. Have you had any reports of that? Is it because of these Feb 8 updates? Just want to make sure this latest build is "safe" to install. ** If anyone else has had issues with these most recent builds from Feb 8 (from the link above), please let me know! Thanks. CORRECTION: Looks like there is a NEW issue. An error people are getting about "Cannot open any more databases" / Locking file left active. So, just want to make sure these latest builds aren't the cause of this new issue. Thanks.

The 2108 Version with the 14000 series build resolves the lockout issue. It will need to be installed on each version of computers you have in your organization.

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

2022-02-22T14:01:19+00:00

Hello Shane,
I have had Version 2108, Build 14326.20738 installed for a few weeks and everything has been working fine. No file locking issues.

I just got an update notice from my Software Center that is wants to install Version 2108, Build 14326.20784Looks like this was released on Feb 8, according to this:
https://docs.microsoft.com/en-us/officeupdates/microsoft365-apps-security-updates

I've seen posts on other pages that the file locking issue may have returned for some people. Have you had any reports of that? Is it because of these Feb 8 updates? Just want to make sure this latest build is "safe" to install.

**If anyone else has had issues with these most recent builds from Feb 8 (from the link above), please let me know! Thanks.CORRECTION: Looks like there is a NEW issue. An error people are getting about "Cannot open any more databases" / Locking file left active. So, just want to make sure these latest builds aren't the cause of this new issue. Thanks.
Was this answer helpful?

0 comments No comments
Anonymous

2022-02-22T14:46:25+00:00

The 2108 Version with the 14000 series build resolves the lockout issue. It will need to be installed on each version of computers you have in your organization.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-02-22T15:21:10+00:00

Thanks Edward!
Was this answer helpful?

0 comments No comments