Dec 16 2021 12:22 AM
Dec 16 2021 12:22 AM
We have a database on a network drive that was set up for multi user concurrent access with the following configuration that had been working well until just recently. Multiple users could work in the database at the same time using the below configuration
Default open mode = Shared
Default record locking = Edited record
Open databases by using record-level locking = Yes
Firstly, the record locking file is not automatically deleting on closing of access when the database is on the network drive. C drive removes the file as per normal behavior.
Unable to open the database when opened by someone else and the record locking file is already created. Error message "already open by another user" or "could not lock records"
I believe read, write and create access to the network drive location is fine as I can manually delete the record locking file no issues.
Only started experiencing this problem after updating Office 365 on December 14. The current build used is Monthly Enterprise Channel, Version 2110 Build 14527.20340 Click-to-Run
Dec 17 2021 04:47 AM
We are also experiencing this exact issue today on two of 8 networked systems that shared the Access Database and both have updated to Version 16.0.14701.20248 (Via 365). First system was updated on 14th Dec and the other one on the 16th .
Have you managed to resolve and , if so, did you roll back to a previous version?
Look forward to your reply
Dec 17 2021 05:49 AM
Dec 17 2021 02:51 PM
Dec 17 2021 03:00 PM
Dec 22 2021 08:20 PM
Dec 23 2021 12:47 AM
Jan 03 2022 09:01 AM
Was not able to get the rollback to work using the deployment tool and
setup.exe /configure config.xml
where the xml file contains:
<Updates Enabled="TRUE" TargetVersion="16.0.14701.20226" />
do you have a suggestion?
Jan 04 2022 04:09 PM
Jan 07 2022 06:59 AM
@Simon0916 we are having the exact same issue with Office Professional Plus 2016 on a terminal server.
Version 16.0.5215.1000 and it started around December 14th.
It only seems to affect databases on a shared drive, if you use the local c: drive there is no issue.
I also noticed that the .laccdb files that get created are 0b which is different from when they are working and they tend to be 1kb.
Doesn't seem to be fixed by latest updates so will try to roll back instead for now.
Jan 12 2022 02:03 PM
Jan 16 2022 03:38 PM
Jan 17 2022 05:47 AM
I am supporting several Access databases using the similar conditions as you described, all of them are affected in the same manner. I am quite sure that this issue is on Microsoft's side.