Cannot open any more databases error 3048

I saw MS's post but I already had TLs in place and my DB was still falling over when running a concatenate module in VBA.

If you look at the bottom of MS's post there is this catch:

**Note:**This workaround will not work if AMSI (Antimalware Scan Interface) is enabled for all documents.

It seems AMSI is used to check VBA macros, which is where my particular probem is. And when I switched off the security on my Access folder everything worked again.

That said, I was on my home PC at the time, now I'm in the office and those settings are not helping on our office PC! Bizarre!

I did look at the rollback option but it just looked a bit daunting as a non programmer. I love Access but I tend to fly by the seat of my pants most of the time. I guess I'll have to give the rollback another look.

Thanks for the feedback.

Great that MS finally got around to posting on this issue at - Fixes or workarounds for recent issues in Access. https://support.microsoft.com/en-us/office/fixes-or-workarounds-for-recent-issues-in-access-54962069-14f4-4474-823a-ff7e5974a570?ui=en-us&rs=en-us&ad=us

@NevilleWootton - thanks for you input, FYI - Recently there was an issue that arose from a MalwareBytes release that caused errors in Access code and did require changing MalwareBytes security settings. And you could say that making those changes opened up a security hole but what you gonna do? Sometimes you need to try less secure just so you can operate until you find a safer solution.

But I do agree with Daniel, in this case a rollback is the best option. https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841

Only the brave would set their updates to Current Channel and Automatic in a production environment. If you are lazy then leave updates as automatic but set your channel to Bi Annual.

That's simply not true Neville and that is opening yourself to a serious security hole. If that truly was required, you'd be best to rollback your build instead, but keep security running.

Even MS indicated that all that is required is the creation of TLs, refer to https://support.microsoft.com/en-us/office/access-is-unable-to-close-and-leaves-lockfile-active-b2dce32b-b8b0-41f1-ba40-7876e524d9da

These settings fixed the 'Error 3048: Cannot open any more databases' bug for me:

ACCESS SETTINGS

Access > Options > Trust Center > Trusted Locations > Trust Center settings > Trusted locations > Access folder location(s)

WINDOWS SETTINGS

Settings > Windows security > Virus & threat protection > Manage settings > Real time protection > Off

Settings > Windows security > Virus & threat protection > Manage settings > Exclusions > Add or remove exclusions > Access folder location(s)

NB. Access > Trusted Locations is not enough to stop this bug, these Windows settings must be used as well.

Thanks Daniel,

I advised my clients to do those 3 steps

1. create a trusted folder for both FE and BE
2. delete orphaned msaccess.exe processes
3. Delete laccdb lock files

They then reported a 3709: The search key was not found in any record followed by the 3048 error

However, I'm not sure that they correctly did the Trusted Folders

and the 3709 is probably a red herring.

They have now asked their IT to roll back to a safe version of 365

pre 2201 but after the last issue.

I specified Version 2108, build 14326.20738

and hopefully they will be turning off automatic updates.

They were on Enterprise Current Channel - duh!