Microsoft Office 365 Build 2201 Causes Access Applications to error
We have received reports and confirmed with Microsoft there is an issue with Microsoft Office 365 build 2201 that causes Access applications to fail with errors usually at the startup but also during use. Because the update is now being rolled out to the users, some users may be affected earlier than others. To avoid disrupting your productivity, we strongly recommend that you use slower channel such as SemiAnnual to get more stability and avoid being hit by bugs like those. Microsoft is currently working on a fix but we don’t know when it will be fixed.
To help those who already has been hit by the bug or are at risk of getting hit by the bug, we’ve prepared a guide to help walk through the diagnosis and resolution and provided it as a PDF documentation.
Instructions for changing channel or reverting version
Click here to download the PDF.
Symptoms
Note: there has been reports of different symptoms so read through all the lists to make sure whether you are experiencing one of possible symptoms.
1) You get an error message: “Cannot open any more databases.”
2) You get an error message: “Resources exceeded.”
3) You get an error message: “The expression XXXXX you entered as the event property setting produced the following error…”
Note: In the screenshot, it shows “On Unload” but that can vary among applications.
A possible workaround:
There are reports where adding both Access backend (if applicable) and Access frontend to the Trusted Locations, it may avoid the bugs. If you wish to continue with current channel, you can try adding the folders where all your Access files are contained to the trust center. This will need to be done on every workstation that needs to use the Access files. Nonetheless, we still recommend changing to semi-annual channel if possible.
If you need further assistance, please feel free to contact us.
If you are stuck or have questions, feel free to contact us.
The just-published release notes for Semi-Annual Enterprise Channel (Preview) say it’s fixed:
https://docs.microsoft.com/en-us/officeupdates/semi-annual-enterprise-channel-preview
Shouldn’t the PDF mention to disable 365 updates after you roll it back so it does not just auto update again?
The PDF covers the steps to change both versions or channels on a single computer. If you’re changing channels, then leaving updates on is probably fine. If you’re changing versions, then you might need to disable the updates temporarily. Sometimes the users doesn’t have the authorization to disable the updates, which is usually the case in an organization. For that reason, we provide a separate instructions to the IT department for preventing updates. Otherwise, yes, you may want to disable the updates.
You’re a lifesaver! I was pretty sure the problem was Microsoft but didn’t know what to do.
Info from MS: https://support.microsoft.com/en-us/office/access-is-unable-to-close-and-leaves-lockfile-active-b2dce32b-b8b0-41f1-ba40-7876e524d9da … To work around this issue, put your database in a trusted location…
Thanks for comment! We’ve heard some reports that this works for some clients as well.