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.

My O365 just updated to Version 2108 build 14326.20738 and I can say the issue is still not resolved. :-(

The version you mentioned fixed it for me. I updated both PCs to 2108 build 14326.20738 on UNC using DFS, opened the file on one PC, then opened on another. If one of your PCs is with a previous Office version then it will fail.

My O365 just updated to Version 2108 build 14326.20738 and I can say the issue is still not resolved. :-( Have you rebooted after update? I'm not certain that should be necessary, but that build should fix the problems. Can you elaborate on what you are seeing?

Ah, that may be my problem. that is good news then that this fixes it.

My issue might be that I had only updated on 1 PC to test and the database was being used by someone with the December version. There are many others in my environment that are still on that version. I will update all in the coming days and see if this issue is resolved.

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-11T16:48:51+00:00

My O365 just updated to Version 2108 build 14326.20738 and I can say the issue is still not resolved. :-(
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-11T17:42:41+00:00

The version you mentioned fixed it for me. I updated both PCs to 2108 build 14326.20738 on UNC using DFS, opened the file on one PC, then opened on another. If one of your PCs is with a previous Office version then it will fail.
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-11T17:49:12+00:00

My O365 just updated to Version 2108 build 14326.20738 and I can say the issue is still not resolved. :-(

Have you rebooted after update? I'm not certain that should be necessary, but that build should fix the problems. Can you elaborate on what you are seeing?
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-11T17:49:30+00:00

Ah, that may be my problem. that is good news then that this fixes it.
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-11T17:57:23+00:00

My issue might be that I had only updated on 1 PC to test and the database was being used by someone with the December version. There are many others in my environment that are still on that version. I will update all in the coming days and see if this issue is resolved.
Was this answer helpful?

0 comments No comments