Cannot open any more databases error 3048

Thanks Karl,

Yep,

I recall when 365 went subscription and it took me days to figure out which plan I needed. At the time none of the Business plans included Access.

Making this task harder was that MVPs got theirs for free so they just went with the most expensive, as I ended up doing. E3.

Now there are 2 different flavours of E2 and the entire suite of plans is even more confusing to the novice.

Channel names have been subject to a rapid evolution of nomenclature.

Then consider Product ID, Version Number and Build Number (have I missed anything?)

Making this all harder is the number of, and changes to, the pages where MS, and specifically Access, posts information about new features, fixes, suggestions, which include pages mentioned in these posts and others.

As I mentioned, the 365 Admin center is blissfully ignorant of all these issues which suggests that 365 Admins (the people) are as well, and as we've seen, so are MS's own support people.

I've thought long and hard (well not so long, but hard) and decided that I'd like to see a series of links (better if it only needed to be one) in the Accounts / About page, in addtion the cringe worthy "Whats New" button, to take me to a web page with proper Release Notes (Features and Fixes) showing all current and previous versions.

That page could then have a link to other relevant pages like suggestions, This forum, Access Blog and any other relevant site for the 365 app it is launced from as well as 365 in general.

The Product Information on the Account form currently does tell you the Subscription Product (in my case Microsoft 365 Apps for enterprise), the Version and Build. So it is reasonably aligned with the terminologies on the web sites but not entirely.

Now I don't expect developers to ever care about this stuff, but the Product Manager(s) for 365 and in this case Access should.

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.