Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
The refresh of a dataset on PowerBI service fails and the error given is "We're sorry, an error occurred during evaluation.;The evaluation reached the allowed cache entry size limit. Try increasing the allowed cache size.. The exception was raised by the IDataReader interface.". Locally the refresh is completed without any issue. We are using pro licenses. The size of the dataset is ~400Mb and its sources are Azure SQL Database and Excel Files located on Sharepoint Online. No Power BI Gateway is being used to refresh the data on the service. I have increased the maximum allowed Mbs of Data Cache Management locally on PowerBi desktop.
I can't find any reference about the cache usage and how I can reduce it on the dataset or even which are its limits on Power BI service. It seems like a black box. The problem started after I added some data (minor in terms of volume) from excel files on Sharepoint online, I don't know if it is a coincidence.
Any help and guidance would be highly appreciated!
Best
Solved! Go to Solution.
hey, try reducing the number of simulstanious evaluation it does in addition to increasing the maximum MB permit per evaluation(that you aleady did).
also try to norrow down the query giving you the error you can run each query one by one and see the amount of time taking each one and the amount of data its pulling. them send over the query script to see if theres a optimization issue with the code.
if all fails also open a support ticket for microsoft since they can provide you additional information on the server error its giving you if you cant access any more information about the incident to determine (also try running each query as a dataflow to see how its behavite in the web service).
hope this give some orientation to start with
Proud to be a Super User!
hey, try reducing the number of simulstanious evaluation it does in addition to increasing the maximum MB permit per evaluation(that you aleady did).
also try to norrow down the query giving you the error you can run each query one by one and see the amount of time taking each one and the amount of data its pulling. them send over the query script to see if theres a optimization issue with the code.
if all fails also open a support ticket for microsoft since they can provide you additional information on the server error its giving you if you cant access any more information about the incident to determine (also try running each query as a dataflow to see how its behavite in the web service).
hope this give some orientation to start with
Proud to be a Super User!
The answer was in "try running each query as a dataflow to see how its behavite in the web service". When I moved the queries on dataflows I was able to spot the query giving the error.
Thank you very much for your response.
I reduced simultaneous evaluations but with no luck. I reduced the complexity (removed some merge steps) of some of the queries but still get the error.
Currently I am moving the queries to dataflows but it is considerable work.
I will come back with feedback later.
Best
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
57 | |
35 | |
27 | |
27 | |
26 |
User | Count |
---|---|
62 | |
51 | |
30 | |
24 | |
23 |