Forum Discussion
Cannot Open any more databases
This message often occurs when Access has used up all available connections.
See my utility Available Connections which you can use to check the issue and from that work out what needs to be changed to solve your issues
Hi, I am having a similar problems. Could I try your utility?
I tried to download but message stated that the page is not available
Thanks
Harris
- Feb 04, 2022
Hi,
If your version is M365 Current Channel version 2201 build 16.0.14827.20158 then you are most likely one of the victims of the latest update bug. In this case you should read one of the many existing discussion about it here, especially this one.
Servus
Karl
************
Access News
Access DevCon- Harris_StFeb 04, 2022Copper Contributor
Hi Karl,
Thanks for letting me/us know.
I have been tearing my hair out trying to understand what is happening.
At least I can now appreciate what is the cause for my teams databases falling over.
Regards,
Harris
- isladogsFeb 04, 2022MVP
Hi
Sorry about the broken link. My old http website is no longer in use
The utility is still available from my new website:https://www.isladogs.co.uk/available-connections
I've also fixed the earlier link
A lot of people have contacted me in the past couple of days about this utility and it can be very useful to diagnose issues.
However, in case you aren't aware, there is another major bug in the recent update to Office 365 - version 2201 build 14827.20158 - which is triggering the cannot open any more databases error.
There have been a very large number of forum posts on the issue around the world.
MS are aware of the issue but have not yet commented publicly on it AFAIAA
- Harris_StFeb 04, 2022Copper ContributorThank you very much!
Harris- fogelfishFeb 07, 2022Copper ContributorI'm glad I found this thread. It lowered my anxiety level from high to moderate. I have a couple of questions: (1) does anyone know where or how I can keep tabs on this bug's eventual resolution? and (2) has anyone yet come up with some way to work around this bug while it's still unresolved?