Forum Discussion
The XML for Analysis request timed out before it was completed. Timeout value: 225 sec.
Hi,
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.
9 Replies
v-huizhn-msftMicrosoft Employee
Hi wenthe,
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.
http://community.powerbi.com/t5/Service/visual-has-exceeded-available-resources/td-p/115962
Best Regards,
AngeliaHi Angelia,
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?
Thank you,
Wenting
- v-huizhn-msft
Hi wenthe,
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.
Best Regards,
Angelia
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
Activity ID 8eef8ef7-75c3-4e21-8ec6-6591cbdaedc2Correlation ID08d10bec-358a-e348-aa94-0565122a8405Request ID cec6f519-82eb-daab-25fd-8dabab5abf38The 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
Activity ID 8eef8ef7-75c3-4e21-8ec6-6591cbdaedc2Correlation ID08d10bec-358a-e348-aa94-0565122a8405Request ID cec6f519-82eb-daab-25fd-8dabab5abf38
AllegroHelper I
Hello
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
javier
- Allegro
hello wenthe
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
javier
