Cannot open any more databases error 3048

Hi Kent,

> Presumably, this channel is now infected with the new issue at the same time the Current Channel got a fix???

I don't think so, as the Monthly Enterprise channel build is later and higher than the December bug fixing build and lower than the Jan/Feb bug introducing build of the Current channel.

From such a sentence you can see that the many versions, channels and builds are of course a massive problem. They may be suitable for software engineers at Microsoft who know their builds and forks. But they are a disaster for communication with the outside world. Even we as experts often lose the track, let alone the average customer.

In its urge to provide every type of customer with the appropriate variant, Microsoft has gone way overboard to the point of complete confusion. IMPOV, it would be time for a comprehensive reform and simplification in Office distribution and communication, because it is getting worse and worse. This is of course especially noticeable in times of such crises with update bugs.

Thanks for the release notes link Karl,

That page shows details for the last two releases for the Current Channel

Version 2201 (Build 14827.20158)

Version 2201 (Build 14827.20192) released Feb 8

The first fixes the previous issue, and presumably introduced the new issue

The second fixes the current issue.

But if you look at the table regarding fixes for the previous issue Version 2112, build 14729.20248 as the build to fix it for the Current Channel

https://support.microsoft.com/en-us/office/error-in-access-when-opening-a-database-on-a-network-file-share-6cbc1560-62c2-46e7-9980-d079a46f5acc

it points to Version 2112, build 14729.20248 as the build to fix it for the Current Channel

Now ain't that beezzarre!

I do not understand the Version Number system they use (and it looks like they don't either) and that combined with the multiplicity of Channels and Builds is doing my head in.

But wait there's more...

There is no mention of a fix to the current issue in either the Enterprise Semi Annual or Enterprise Semi Annual(Preview)

Stranger and stranger...

Then when we peek into the Monthly Enterprise channel Version 2112 (Build 14729.20322) released Feb 8 we find
Access

• We fixed an issue that caused the Insights add-in to stop working intermittently.
• This change enables full support of requirement set 1.11 and 1.9 for Outlook add-ins.
• We fixed an issue that would prevent multiple users from opening a database on a network file share. Learn More
• We fixed an issue that caused an application to close unexpectedly when connection to an Access or Jet database using multiple threads.
• This change fixed an issue that may cause an application that used the OLEDB API to open an Access database (.accdb file) to close unexpectedly if the database contains links to SharePoint lists.

you will note the third item which refers to the previous issue. Presumably, this channel is now infected with the new issue at the same time the Current Channel got a fix???

Cloister Fudge.

I would never have known about that page if you hadn't provided a link. I just don't get why the main Access fixes page still hasn't been updated to reflect this more than 24hrs after the fact.

Just another Microsoftism.

Hi Daniel,

The only public Microsoft statement so far about the fix can be found in the release notes for the build from yesterday.

They were published 1 day after the build and for the average user they are of course hard to find.

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.