I encounter this error after publish a desktop normal report to the website.
One of the visual can not show normally while other peer visual look fine.
The data source of the report consume a SQL view which have only 27771 records and the data is connected in DirectQuery mode.
My question is, why only one of the visual cannot be diplayed normally? The whole report comes from a same SQL view.
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.
im going through the same error "The XML for Analysis request timed out before it was completed. Timeout value: 225 sec."
in my experience problems like this suddenly disapper but id like to know more about it, also currently all my datasets are timing out the refresh were before only took 10 to 15 minutes. my data source is big query
if you found the rooth cause of the error id like to know
Right now we are discussing exactly the same error on Premium Capacity P1 "The XML for Analysis request timed out before it was completed. Timeout value: 225 sec."
support case 19082224000874
The error suddenly appeared and then suddenly disappeared without our activity.
The process is a bit confucing:
1. Support suggested to optimise all queries on all visuals and the whole model.
2. As soon the error suddenly disappeared without any action from our side support became happy but we insisted to discover the root cause because the error may suddenly appear again - surprisongly we have to explain it to the suport.
3. Support suggested to use fidder next time the error appears - a bit strange idea.
4. Currently i am insisting there should be useful information in some kind of logs behind the following ids and curious why support dows not want to discover it
im going through the same error on Premium Capacity P1 "The XML for Analysis request timed out before it was completed. Timeout value: 225 sec."
in my experience problems like this suddenly disapper but id like to know more about it, also currently all my datasets are timing out the refresh were before only took 10 to 15 minutes.
did you find the rooth cause of the error? id like to know
It returns the error, because your visual has attempted to query too much data to complete the result with the available resources. You'd better try filtering the visual to reduce the amount of data in the result. You can see the error in this troubleshooting article: Troubleshooting tile errors.
And I post a similar thread below for your reference. Hope it's useful.
Thank you for your reply.
As I mentioned, all the visual in the report query the same SQL data, why only one of them cannot be displayed normally in website? (It works fine in desktop.)
I have limited the date in the SQL view to reduce the output of the SQL view, no more than 50k rows come from the result of the SQL view. What's the limitation exactly? What else can I do to filter the abount of data?
There is no restriction on how large a pbix file can be locally. However, when you publish a pbix file over 1GB to Power BI Service, please check the size of your .pbix file.
Watch the playback when Priya Sathy and Charles Webb discuss Datamarts! Kelly also shares Power BI Community updates.
Watch Session 24 of Ted's Dev Camp along with past sessions!
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.