Forum Discussion
BUG::TIMEOUT PERIOD ELAPSED::POOL ERROR::IDbConnection interface
ISSUE:
Power BI Desktop has a report open. The report is connected via DirectQuery to a dim table in a LH. The has only 2 columns and 2 rows.
After leaving a report page for more than an hour and working on a different page, I navigate back to the previous page and find out that one slicer linked to this dim table in the LH is showing as broken. I click on See Details and this error pops up:
Before anyone says it's a Power BI Desktop issue, please read the error message: It mentions that a max pool size was reached, which seems to indicate something went awry with the connection pool manager at the server level, not the local app since I don't have that many connections to Fabric from this report, in fact only 8 tables, assuming 1 connection per table.
The issue didn't reoccur without me doing anything... so obviously something on the backend got fixed or it is randomly intermittent and will rear its ugly head again.
6 Replies
Hi Element115
Thanks for using Microsoft Fabric Community.
Apologies for the inconvenience.
The error message indicates that the Power BI slicer linked to the dim table in the live connection is experiencing a timeout issue.
- Click on "Refresh" in the Power BI Desktop ribbon. This might establish a new connection to the LH and resolve the timeout issue.
- In some cases, a corrupted slicer object might be causing the issue. Try deleting the current slicer and recreating it from the dim table in the LH.
- If a connection issue is suspected, delete the existing relationship between the dimension and fact table. Subsequently, re-establish the relationship using the appropriate columns. This process can sometimes help resolve connection errors.
I hope this information helps. Please do let us know if you have any further queries.
Thank you.
Hi Element115
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.Thanks.
Thanks.
On closing/reopening the report, the slicer reloaded normally. I do notice though that all slicers seem to have long load time. These are linked to small dim tables stored in the LH, so it's kind of puzzling why the load times in DirectQuery are so slow for what amounts to 2 - 10 row tables with no more 3-10 columns.
