Forum Discussion
visual has exceeded available resources
Hi jgarciabu,
Yes, the issue occurs when a visual has attempted to query too much data for the server to complete the result with the available resources.
As suggested in the error, you may need to try filtering the visual to reduce the amount of data in the result currently.:smileyhappy:
Regards
Hi jgarciabu,
Yes, the issue occurs when a visual has attempted to query too much data for the server to complete the result with the available resources.
As suggested in the error, you may need to try filtering the visual to reduce the amount of data in the result currently.:smileyhappy:
Regards
I don't think this issue is solved. What are the actual limits, and are they the same for all visuals? I'm having this issue with a simple date filter which is querying a view that has only a few thousand rows. We barely have 1.5 years of data, this is pathetic.
Is this a limitation in the Power BI Web Service?
I'm also working with a fairly large DAX calculation - it works fine on my Desktop environment, but fails to load as soon as it's published.
Why is this issue marked as solved? What is the "available resources" and what is the solution?
In my instance, some users are seeing this issue in the PowerBI service and some are not. How do I deal with this kind of issue? It would be terrible to believe a visualization is working properly, go out on a sales opportunity to a client and have this fail like this.
This answer is not acceptable.
This simply does not make any sense without considering the data size, result size, type of visuals etc.
For intsnace, In my POC environment there are 34000 Rows even after all the joins. I have a tabular view which is displaying not more than 40 Rows currently (8 Columns).
As soon as I try and add Another column, the visual fails.
One of the column is a Measure returning Data in relevant currency.
I can't understand How inefficient my query could be to make resources so scarce !
I'm having the same issue with a visual that uses 2 DAX fields to calculate cumulative profit $ between 2 dates, this year and last year. The visual is just a line graph. It was fine until 4-5 days ago.
This is annoying since the visual is exactly what the UI and DAX should be for..
This happens so intermittently and at random times it would be nice to know if there is something that can be done when it happens. At times it works fine so there has to be a setup where the stars align, what is that sweet spot and how do we get our visuals to that nirvana so it can be refreshed more reliably?
Great no help answer.
I seem to run into the same issue but:
This issue only occurs on certain machines opening the report.
So what calclulations / ressources are used here?
The page / visual loads within 10 - 15 seconds on my pc, same for my co workers mac.
The mac in the warehouse fails and gets the error.
We all are on the same network.
The errormessage is as useless as the post marked as "solution".
If you're running into this problem when opening the report in Power BI Desktop, the reason it works on some machines and not others is that some machines will have more resources (most likely memory is the key) than others. There are settings you can change in Power BI Desktop to control how much memory is available for your semantic model: https://blog.crossjoin.co.uk/2023/06/18/the-visual-has-exceeded-the-available-resources-error-in-power-bi-desktop/
However if you are encountering this error when opening the report in a browser then you're running into issues - again probably memory related, but you need to check the error message - in the Power BI Service. I recently wrote a series of posts on this subject starting here: https://blog.crossjoin.co.uk/2024/04/28/power-bi-semantic-model-memory-errors-part-1-model-size/ If you scroll to the bottom of that post you'll see links to others in the series; you should read the post on the Query Memory Limit and look at the posts on bad practices that can cause this problem.
This explains the error but not help solving the problem. I happen to notice one of my DAX measure used switch function, that consumes lots of capacity:
Reporting Amount Base_PL = SWITCH([Selected Currency],1,[Group Currency Amount Base_PL (EUR)],2,[Company Currency Amount Base_PL],3,[Budget Currency Amount Base_PL (EUR)],4,[USD Amount Base_PL (USD)])
to reduce the resource need, I stop using the switch function and use the sub measures directly.
