visual has exceeded available resources

[jgarciabu]

Hi All,

I've been using PowerBI for the better part of a year now. For the last month and a half or a little more, we've had annoying failures to refresh for 6 of our 14 tile visualizations. It's also inconsistent. Some days certain tiles of the 6 refresh and others they don't. The dashboard in question contains nothing more than 14 pinned single data point cards. They are simple queries made to our Azure SQL Database. On the database, all the queries run immediately with no delay. I have all my visualizations set to connect live to our Azure database. I'm at a loss for what to do. It seems like it's an issue with resources on Microsoft's servers. Here's the error I get:

Resources Exceeded

This visual has exceeded the available resources. Try filtering to decrease the amount of data displayed.
Please try again later or contact support. If you contact support, please provide these details.

Activity IDc7b563f3-c93d-2aa1-2784-082b8d81f234

Request IDe4c3c75a-060f-6b40-8ab0-7ed194ba10c3

Correlation ID69832fcb-c121-4ed4-ca06-89d5275e48e2

TimeThu Jan 19 2017 11:09:24 GMT-0500 (EST)

Version13.0.1700.1003

Cluster URIhttps://wabi-us-north-central-redirect.analysis.windows.net

[CahabaData]

interesting to hear.  in your comparison - how much RAM locally is it taking a good chunk of??  are you up in the 32G area on a server or more?

[malagari]

I'm able to run some of the measurements without issues on my 12GB RAM Windows VM, but it doesn't cooperate when I have multiple card visuals with different measurements on the same report page.  On my desktop, I have 32GB of RAM and I'm able to render everything properly.

The "big" DAX calculation can take upwards of 18GB of RAM when making the date comparisons.  It really only gets bad on my desktop when I have more than one visual doing a fairly large calculation against a table of ~40K rows.

It's at the point where I'm investigating if OLAP Cubes would help improve the performance of my historical data (again, offloading the strenuous calculations to an SSAS instance).

[CahabaData]

interesting - thanks for sharing... 

[v-ljerr-msft · Accepted solution]

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.

Regards

[GaigeDaois]

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".

[cpwebb]

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-pow...

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.

[GaigeDaois]

I was able to find the or at least some sources of this issue for my reports.

Biggest cause were nested IF-functions, which I replaced by using SWITCH.

Performance for all useres of the online report improved.

[Jeanxyz]

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. 

[cpwebb]

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-d... So it may be possible to keep your SWITCH if you do some optimisation.

[GaigeDaois]

Thank you for the reply.

To be more precise (if anyone runs into similar problems), my problem occurs in web browsers opening certain pages in the report.

You have pointed out some causes & solutions in your blog.

I'll report back if I was able to solve the troubles. 

[Drunken_Sailor]

Great no help answer.

[mkruk]

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?

[datablaster5000]

This answer is not acceptable.

[Anonymous]

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.

[skocheta]

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 !

[sxt173]

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..

[corbusier]

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. 

[malagari]

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.