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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-12-22T08:31:25+00:00

    In my department we run 2 tools. One is a multi-user tool with a shared backend on a network drive and we have issues as described. Advancing to build 13801.21092 later today to see if that fixes the issue.Another is a tool that runs locally on PC hard drive with only 1 user. Even here we are affected - it is extremely slow. Have confirmed that rolling back from 16.0.13801.21072 to 16.0.13801.21050 solves the issue. I have logging in place and a loop like this is much slower. Fingers crossed that 21092 will solve this as well. 

    set rs = CurrentDb.OpenRecordset(name:="LocalDBTable", Type:=RecordsetTypeEnum.dbOpenDynaset)  

For each bla in blaCollection.items 'count = 400 items  

    With rs          

        .AddNew  

        !FieldA = bla.aNewValue  

 '....  

        !FieldZ = bla.zNewValue  

        .Update  

    End With  

Next bla  

rs.Close  

set rs = nothing

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-12-21T21:48:45+00:00

    The issue with the MEC update should now be resolved, you should be able to use WSUS\SCCM now.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-12-21T21:36:16+00:00

    There will be an update for Office 2013 soon, but it is not yet available.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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

  5. Anonymous
    2021-12-21T20:14:05+00:00

    Is there a fix for the msi version of Office 2013?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments