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.

Can anyone provide the version number for Semi-Annual Enterprise Channel 2102? I could only update to 2108 but it's hard to guess 2102 :(

Version 2102 is Semi-Annual Enterprise Channel Extended and has not been updated yet. You can move to Version 2108, which is the current Semi-Annual Enterprise Channel version, and has been updated (build 14326.20738), so if you can move to that channel, it will address the issue for you.

Seriously? I have made the tests and I can confirm, it's fixed it only for 2108 ( 14326.20738 ) and not for 2102 ( 13801.21106 )! This is outrageous, 2102 supposed to be stable channel, still supported, we have procedures on the production, we can't change Office version for thousands of users without testing the AddIns and any other Office dependent software. Why fixing only for one build and not the others? And why there are still no 2008 version? This version supposed to be supported until 8th of March 2022, is there a plan to release it? What is going on there?

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

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?

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-11T18:03:43+00:00

Can anyone provide the version number for Semi-Annual Enterprise Channel 2102? I could only update to 2108 but it's hard to guess 2102 :(
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-11T22:27:24+00:00

Version 2102 is Semi-Annual Enterprise Channel Extended and has not been updated yet.

You can move to Version 2108, which is the current Semi-Annual Enterprise Channel version, and has been updated (build 14326.20738), so if you can move to that channel, it will address the issue for you.
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-12T07:41:59+00:00

Seriously? I have made the tests and I can confirm, it's fixed it only for 2108 (14326.20738) and not for 2102 (13801.21106)! This is outrageous, 2102 supposed to be stable channel, still supported, we have procedures on the production, we can't change Office version for thousands of users without testing the AddIns and any other Office dependent software. Why fixing only for one build and not the others?

And why there are still no 2008 version? This version supposed to be supported until 8th of March 2022, is there a plan to release it? What is going on there?
Was this answer helpful?

5 people found 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
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