Forum Discussion
Error RSPortal: obtaining a connection from the pool
- 5 years ago
I've worked on this issue with the support. Issue number is 121020321001710.
There is a demo dashboard with Adventure Works Tabular Model and some slicers and filters.
We've fixed the issue by increasing
<MaxCatalogConnectionPoolSizePerProcess> to 500.
Hi again,
I was able to narrow down the problem:
Some of our older Live Connection Power BI reports don't even open one connection via RSPortal to SQL Server, while others keep increasing the number of connections with each new click (filter, drill down).
I opened one of the old Power BI reports (build with a 2019 desktop version) in my up to date Desktop Version (Oct. 2020) and saved it again to PBIRS.
Now, with each click in this new Version the number of connections increase and i am able to reproduce the error mentioned above.
Looks like a bug in the Desktop Version.
Please advise.
- Petebro5 years agoMicrosoft Employee
Ah let me engage with someone from the desktop team that is more familar with that area I will be back with investigation outcomes.
Though would it be possible to setup an enviroment using the January release of PBI RS And PBI RS Desktop to ensure this wasn't already fixed since October?
- jbarta_mlchc5 years agoHelper III
What browser are you using? I just did some further testing and it does not seem to happen with the new Edge browser. I was wondering if you are using IE 11.
- Anonymous5 years agoNot applicable
I see increasing connections with every browser I use: Firefox (78), Edge (87), Chrome (88).
I don't think this has anything to do with the browser, but with the desktop version that provides the Power-Bi report on the server.- jbarta_mlchc5 years agoHelper III
Thanks for your reply. After understanding where to watch the connections I am now seeing the issue with the new Edge browser as well. I noticed that there were less connection per filter/slicer change with the new Edge browser when compared to IE 11. I was seeing ~24 connections in IE 11 and ~4 with the new Edge. So it took longer for the portal to become unresponsive using the new Edge giving me the false impression that it was resolved using the new Edge browser.