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.

It fixed it for my environment as well.

Do you know if it works on build 16.0.14701.20226

Hi Traci, we had the same versions, the newer update on our channel (version 2108) solved issues.

Shane, or anyone from Microsoft ... I hope you can help me. Where I work, all of us have “Version 2102 (Build 13801.21092) Semi-Annual Enterprise Channel”. And we use standard UNC paths for the back-end. So, according to the MS support site link Shane posted above, that means this issue should have been resolved with the version number we currently have installed, right?? But we are still having this "could not lock" message with multiple users! So why is this still happening? Hoping someone has on here has some answers! Another point of confusion. When I click the “About Access” button, and it brings up the “About Access” pop-up window with license info, etc. It says it’s version 16.0.13801.210 72 . Those last two digits don’t match the version number on the Account page ( 92 ). So, what build number or version number do we REALLY have?

The problem in this case is not related to the update needed for Access but is due to unrelated issues with the Office release process. I am an engineer on the Access team, so I don't have details on what the exact issues are, but an update that includes the full fix will be released for the supported Semi-Annual channels. When the releases are updated, the information will be indicated here: Error in Access when opening a database on a network file share (microsoft.com) Shane

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-01-20T16:53:35+00:00

It fixed it for my environment as well.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-01-20T16:53:14+00:00

Do you know if it works on build 16.0.14701.20226
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-20T16:47:10+00:00

Hi Traci, we had the same versions, the newer update on our channel (version 2108) solved issues.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-01-20T16:06:33+00:00

Shane, or anyone from Microsoft ... I hope you can help me.

Where I work, all of us have “Version 2102 (Build 13801.21092) Semi-Annual Enterprise Channel”. And we use standard UNC paths for the back-end. So, according to the MS support site link Shane posted above, that means this issue should have been resolved with the version number we currently have installed, right?? But we are still having this "could not lock" message with multiple users! So why is this still happening? Hoping someone has on here has some answers!

Another point of confusion. When I click the “About Access” button, and it brings up the “About Access” pop-up window with license info, etc. It says it’s version 16.0.13801.21072. Those last two digits don’t match the version number on the Account page (92). So, what build number or version number do we REALLY have?
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-12T22:24:15+00:00

The problem in this case is not related to the update needed for Access but is due to unrelated issues with the Office release process.

I am an engineer on the Access team, so I don't have details on what the exact issues are, but an update that includes the full fix will be released for the supported Semi-Annual channels.

When the releases are updated, the information will be indicated here: Error in Access when opening a database on a network file share (microsoft.com)

Shane
Was this answer helpful?

0 comments No comments