Cannot open any more databases error 3048

Microsoft SUCKS at communication! Always have and don't seem to want to change their ways.

I heard about the fix from Karl Donaubauer. I never heard about it from Microsoft.

Even if you check the official page on the subject, https://support.microsoft.com/en-us/office/access-is-unable-to-close-and-leaves-lockfile-active-b2dce32b-b8b0-41f1-ba40-7876e524d9da , as of the writing of this reply, there is no mention of the new build or that it resolves the issue. They still have it indicating to use the TL workaround (with no instructions on how to create them, especially for runtime users!).

All I can say, is I totally relate to everyone's frustrations. We, the MVPs, have brought the same issues up to Microsoft for years, and yet here we are, nothing ever changes. That is why I try to post such issues on my own blog as it takes Microsoft days to publish anything, which is sheer madness. The problem is I'm not being paid and I end up spending a tremendous amount of time doing so.

I don't know anymore than you why Microsoft is so slow, unresponsive. Why even when they internally know about the issue, the support agents don't and are still advising users incorrectly. ...

This, and many other bugs, clearly illustrates just how disconnected Microsoft is from its community and how poorly managed their fixes webpages are. It has also clearly demonstrated major internal communication and testing flaws that exist in the testing and release processes which have been ongoing for years now, with no signs of ever being fixed. Don't expect anything to change!

Fun times we live in.

Daniel, and All,

Fabulous that MS resolved this in quite good time. And thank you, Daniel, for posting about a new release.

But it must be said that communication regarding these kind of issues must be improved.

So Daniel, what does "There are some reporting the issue has been resolved" actually mean?

and how was anybody supposed to know a new build, that addressed the issue, had been released?

I'm guessing that the release of this new build was "leaked" to one or maybe a few insiders / MVPs.

Either that or someone was constantly clicking the "update now" button until a new build showed up. Highly unlikely.

------ The current methodology of relying on Forums and MVPs to manage these kind of issues is far from acceptable or professional --------

Did you get that MS? This is important,

AND FYI - I checked my 365 Admin Message Center for any warnings, messaes or updates.

Nothing. Nada.

For users who even know about the "Fixes or workarounds for recent issues in Access" page,

MS were very slow to post the issue when it was first reported and confirmed

I'm guessing that they didn't post until they had the work around.

But in the mean time...

Even users who know about this page were left in the dark and wasting time trying to figure out why they were having issues.

As a developer, I've wasted almost a full day advising clients on how to fix and/or avoid this issue.

And even though there is, apparently, a new build released, the is still no mention of it on the Fixes and Workarounds page.

HI Daniel. Many thanks to yourself and all others contributing to efforts to resolve this. issue. I have carried out the latest update from Microsoft and all is now well. Regards. Geoff

I do note the line

 <Updates Enabled="FALSE" />

that made me smile

but are you sure you want 64 bit?

OfficeClientEdition / architecture / bitness

For those attempting this on their own at home you may need to know a few configuration options before you dive in

like Product ID https://docs.microsoft.com/en-us/office365/troubleshoot/installation/product-ids-supported-office-deployment-click-to-run?redirectSourcePath=%252fen-US%252farticle%252f77654e77-aaeb-4ed6-84eb-1d8b0e086590 and a few other settings https://docs.microsoft.com/en-us/deployoffice/office-deployment-tool-configuration-options

There are some reporting the issue has been resolved and you need to update to version 2201 build 14827.20192‬, but the official documentation does not reflect this.