Forum Discussion
Error while refreshing from service
We found the issue. We never stopped a second to check the basic configuration. The problem was the configuration of the ODBC where the Gateway is located.
Thanks!
Hi. You can try expandind the timeout window. By default, the odbc datasource has 10 minutes timeout, if your source takes longer then it throws the error. You might have been ok for 1 year, but the table was probably growing all that year. You can open the original pbix file with Power Bi Desktop and change it at Power Query Editor. Check the source step and the docs:
https://learn.microsoft.com/en-us/powerquery-m/odbc-datasource
You can change the commandtimeout. Add a parameter like [ CommandTimeout = #duration(0,0,20,0) ]
That is a 20 minutes duration for the timeout.
I hope that helps,
I dont know if I am setting it wrong. I tried to do it in the specific table that's refrenced in the timeout error. I entered the advanced query editor and added the parameter. It looks like this:
let
Source = Odbc.DataSource("dsn=RamosDesa", [HierarchicalNavigation=true], [CommandTimeout=#duration(0,0,40,0)]),
VW_PROTOCOLOESTUDIOS_View = Source{[Name="VW_PROTOCOLOESTUDIOS",Kind="View"]}[Data]
in
VW_PROTOCOLOESTUDIOS_ViewWhen I save that change however, I see an error with the table itself:
Expression.Error: 3 arguments were passed to a function which expects between 1 and 2.
Details:
Pattern=
Arguments=[List]The Hierarcy function is already there in every query. Should i add the commandtimeout in another instance?
I am trying to answer with a new reply but i think i'm adding symbols that seem like HTML and my answer is getting erased.
We did a new test with trying to refresh from service a new dataset with only 1 table (the one referenced in the error)
We are getting an error that indicates that the table is empty. "there's no visible columns in the table and data cannot be queried" (translated from spanish). Pretty sure this is whats causing the error as it times out trying to read data thats apparently not there.
The thing is that the table HAS data and there are no transformations applied to it.
Any hint?
Ok, now it sounds like there is a problem on the View you are getting from the source. You could refresh the view at Power Bi Desktop and check if it has data and how long it takes to know the timeout too.
But if it's coming blank, it sounds like a process on the backend was't ready or there is an issue with it.
Regards
We found the issue. We never stopped a second to check the basic configuration. The problem was the configuration of the ODBC where the Gateway is located.
Thanks!