Forum Discussion
This visual has exceeded the available resources
Hi All,
We are getting the below error after uploading the dashboard into Power BI Service.It works fine at Power BI Desktop.
"This visual has exceeded the available resources. Try filtering to decrease the amount of data displayed.
Your visual has attempted to query too much data for us to complete the result with the available resources. Try filtering the visual to reduce the amount of data in the result."
Can you help us to look into this issue?
Hi Anonymous ,
Based on your description, my interpretation is: When you run a DAX query in Power BI it will always use a certain amount of memory; inefficient DAX calculations can cause a query to try to grab a lot of memory. In Power BI Desktop these queries may run successfully but be slow, but the Power BI Service can’t just let a query use as many resources as it wants (if it did, it may affect the performance of other queries being run by other users) so there is a resource governor that will kill queries that are too resource hungry. In the case of the visual above the query behind it tried to use more than 1GB of memory and was killed by the resource governor.
If you are Power BI Shared Capacity, you cannot change the resource limits. However, you can change many different settings on the capacity in Advanced Capacity to meet the requirements.
Also, the best way is to optimize your data model. And adjust the DAX calculation used in this visual object. Then republish to service.
For more details, you can read below blog:
The VertiPaq Engine in DAX | Microsoft Press Store
If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
gauthamboppanaSolution Specialist
Anonymous - Looks like the visual is taking too much time to render or load. Please check the below.
1) If you have Datetime fields, change them to Date
2) Check if the DAX calcualtions behind the visual are optimised.Did I answer your question? Mark my post as a solution! If not, please feel free to ask me.
Also, I would ❤ Kudos if my solution helped. It is a token of appreciation!
Thank you very much !
v-henryk-mstfCommunity Support
Hi Anonymous ,
Based on your description, my interpretation is: When you run a DAX query in Power BI it will always use a certain amount of memory; inefficient DAX calculations can cause a query to try to grab a lot of memory. In Power BI Desktop these queries may run successfully but be slow, but the Power BI Service can’t just let a query use as many resources as it wants (if it did, it may affect the performance of other queries being run by other users) so there is a resource governor that will kill queries that are too resource hungry. In the case of the visual above the query behind it tried to use more than 1GB of memory and was killed by the resource governor.
If you are Power BI Shared Capacity, you cannot change the resource limits. However, you can change many different settings on the capacity in Advanced Capacity to meet the requirements.
Also, the best way is to optimize your data model. And adjust the DAX calculation used in this visual object. Then republish to service.
For more details, you can read below blog:
The VertiPaq Engine in DAX | Microsoft Press Store
If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.