Forum Discussion
visual has exceeded available resources
- 9 years ago
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
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.
- cpwebb2 years agoMicrosoft Employee
You might be running into the issue with SWITCH, disconnected tables and key columns that I discuss here: https://blog.crossjoin.co.uk/2022/09/19/diagnosing-switch-related-performance-problems-in-power-bi-dax-using-evaluateandlog/ So it may be possible to keep your SWITCH if you do some optimisation.