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,
I think we have the same problem.
I see the same error-message in our "rsportal"-log. We are using oct 2020 version (15.0.1104.239) of the server.
I have tried to reproduce it and for some reports (in my example it was a Live Tabular report) i can increase the number of SQL connections by for example changing a filter/slicer in the report. But in my test it seems like I can increase the number of conection to a certain level (can be below 100) by changing a filter, but then it just stop increasing it. I´ve not been able to "kill" the report-portal while doing my own tests.
I´ve never been able to get a higher number of connections than 100.
I´m also looking in the sys.processes view to count the number of connections to 'RSPORTAL'.
I´m not sure which version of the desktop the user that created this report where using. Can I see it in some way (perhaps in the reportserver database)?
I´ve got calls from users saying the report portal is sometimes not responding and I think it is because of this problem.
- jbarta_mlchc5 years agoHelper III
I am trying to understand further how you are seeing the connections. I see a view called sys.sysprocesses and I run that against the PBIRS database. What should I be looking for to see the connection and seeing them increase? Thanks for you help in understanding this further.
- jbarta_mlchc5 years agoHelper III
Nevermind I figured it out and now I can see the connections increase. I did some testing with the new Edge browser versus IE 11 and one thing I noticed is that there were far less connections per filter or slicer change in the new Edge versus IE 11. I was seeing it increase by ~4 connection in the new Edge and around ~24 connections in IE 11 with each filter/slicer change. It took a lot more changes to reach the 100 before the portal became unresponsive.