Forum Discussion
Connection Timeout Issue
Hi,
I'm having an issue with a visual (table with many columns) which says it exceeded the available resources after publishing it.
The error details are "The XML for Analysis request timed out before it was completed. Timeout value: 225 sec".
I noticed every time I try to open it, timeout value is always 225 sec so wondering if there is any way to increase this value. I already extended Command Timeout to 1 hour by adding below M code in queries.
Source = Sql.Databases("Servername", [CommandTimeout=#duration(0, 1, 0, 0)])
Or is there any other solutions except optimizing the report?
Thank you.
Note that there is a difference between connection timeout and command timeout. You can specify both.
In your case the reason may be different. Talk to the database administrator to see if they are enforcing a timeout on their side.
9 Replies
Needs more details. Is this Direct Query or Import Mode?
It's Import Mode.
Note that there is a difference between connection timeout and command timeout. You can specify both.
In your case the reason may be different. Talk to the database administrator to see if they are enforcing a timeout on their side.
Hello Ibendlin, i am having this problem with a Direct Query (Originally it was a live connection to semantic model built on Fabric lakehouse, then it fell down to direct query, when i tried to create a new column). When draging one of the DateTime columns to a slicer, i am getting the same exact error. i should admit that my datetime columns has billions of values as i am capturing ms in that column. Is there any thing i can do to overcome this error?
i should admit that my datetime columns has billions of values as i am capturing ms in that column. Is there any thing i can do to overcome this error?Direct Query has a hard 1 Million row limit.
Split your datetime column into a date part and a time part. Use only the date part for the slicer.
Drop the slicer and use the filter pane instead with Advanced Filtering.
On Desktop App go to Options/Report settings/Query Limit simulations. Change from Auto (Memory (1GB) Timeout Limit: 225 seconds) to custom.
