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.

Hi Christine, Fixing this issue is absolutely a top priority. There is a fix available now that addresses the issue for most customers for all versions. There are some remaining issues (e.g. customers using Distributed File System Namespaces will still have problems), which will be fixed soon. Shane

Shane is there a defect number we can follow to be made aware of the final fix being published for this?

I'm not sure what you mean by "defect number", but this article: Error in Access when opening a database on a network file share (microsoft.com) , will be updated with information as the new fix becomes available.

When will it be fixed for Office 365?

When will it be fixed for Office 365? I have a ticket opened and I’ve heard January 11th as potential release date for office 365 current channel. But not an official answer.

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-05T18:23:51+00:00

Hi Christine,

Fixing this issue is absolutely a top priority. There is a fix available now that addresses the issue for most customers for all versions.

There are some remaining issues (e.g. customers using Distributed File System Namespaces will still have problems), which will be fixed soon.

Shane
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-07T09:53:20+00:00

Shane is there a defect number we can follow to be made aware of the final fix being published for this?
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-07T16:54:08+00:00

I'm not sure what you mean by "defect number", but this article: Error in Access when opening a database on a network file share (microsoft.com), will be updated with information as the new fix becomes available.
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-10T07:46:09+00:00

When will it be fixed for Office 365?
Was this answer helpful?

0 comments No comments
Anonymous

2022-01-10T18:02:08+00:00

When will it be fixed for Office 365?

I have a ticket opened and I’ve heard January 11th as potential release date for office 365 current channel. But not an official answer.
Was this answer helpful?

0 comments No comments