Lock File Problems with Access 16.0.13801.21086

Anonymous
2021-12-14T12:18:17+00:00

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:

  1. 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).
  2. Use DAO to OpenDatabase for shared (non-exclusive) access. Error 3050 (“Could not lock file.”) is thrown and the database is not opened.
  3. 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.

Microsoft 365 and Office | Access | For business | Windows

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

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-01-21T19:57:06+00:00

    Have you tried deleting the lock file? It will have a .laccdb or .ldb extension.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-01-21T19:58:37+00:00

    I can't think of any way for that to happen. The file is locked because Access opens it for exclusive access. Once Access closes the file, it should be unlocked.

    You could try deleting the .laccdb file, if it is there, and close Access, rather than just closing the database file (and confirm using Task Manager that Access has quit)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-01-21T20:04:24+00:00

    Yes we do clear the lock file and still the database file stays locked or in use by another user. This happens even with the user showing they have it open closes out the file.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-01-21T21:11:52+00:00

    I have two versions and different builds showing on my machine for Access after we pushed out the latest update

    Under Product Information after the fix was installed:  For MS Access shows: Version 2108   Build 14326.20738

    Under About Access it reads:  Microsoft® Access® for Microsoft 365 MSO (16.0.14326.20702) 32-bit

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-01-21T21:16:41+00:00

    On a desktop machine we performed the fix on I am showing the following

    Under Product Information after the fix was installed:  For MS Access: : Version 2112   Build 14729.20260

    Under About Access it reads:  Microsoft® Access® for Microsoft 365 MSO (Version 2112 Build 16.0.14729.20224) 32-bit)

    On a machine we have not installed the updates on I show the following

    Under Product Information on a machine after the December update:  For MS Access: : Version 2102   Build 13801.21086   

    Under About Access it reads:  Microsoft® Access® for Microsoft 365 MSO (16.0.13801.21072) 32-bit)

    Was this answer helpful?

    0 comments