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.

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.

Yes, the February 1st patch for Office 2016 (and Office 2013) should resolve the issue. Shane Groff Access Engineering

You have build 13801.21092, which has the fix for UNC paths. (the 13801.21072 is specifically the build number on specific component, which wasn't updated in this case so it has an older build number.) However, there are some issues that the fix may still not address (e.g. if you have 8.3 file names), so it is possible there is another issue you are hitting. Semi-Annual channel has updated to Version 2108, build 14326.20738, and that does have the full fix, so the recommendation is to move to that build. Shane Groff

From MSFT: New builds with the fix have started rolling out for some channels: Current Channel: 16.13801.21092 Current Channel (Preview): 16.0.14729.20170 Semi-Annual Channel (Preview): 16.0.14326.20272 Semi-Annual Channel: 16.0.13801.21092 Semi-Annual Channel (Extended): 16.0.13127.21846 For anyone who has seen the issue on one of these channels, if you have the opportunity, please Update Now (it may not happen automatically) to get the updated version and validate that it addresses the issue.

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: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-04T14:59:22+00:00

Yes, the February 1st patch for Office 2016 (and Office 2013) should resolve the issue.

Shane Groff

Access Engineering
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-01-21T00:11:40+00:00

You have build 13801.21092, which has the fix for UNC paths. (the 13801.21072 is specifically the build number on specific component, which wasn't updated in this case so it has an older build number.) However, there are some issues that the fix may still not address (e.g. if you have 8.3 file names), so it is possible there is another issue you are hitting.

Semi-Annual channel has updated to Version 2108, build 14326.20738, and that does have the full fix, so the recommendation is to move to that build.

Shane Groff
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator

2021-12-17T01:41:23+00:00

From MSFT:

New builds with the fix have started rolling out for some channels:

Current Channel: 16.13801.21092

Current Channel (Preview): 16.0.14729.20170

Semi-Annual Channel (Preview): 16.0.14326.20272

Semi-Annual Channel: 16.0.13801.21092

Semi-Annual Channel (Extended): 16.0.13127.21846

For anyone who has seen the issue on one of these channels, if you have the opportunity, please Update Now (it may not happen automatically) to get the updated version and validate that it addresses the issue.
Was 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