Forum Discussion
Data refresh error:The exception was raised by the IDbCommand interface
Hi,
Recently i've been running into this issue where I am unable to schedule refresh or refresh my data from the Power BI online client.
My dashboards are connected to SQL and it has worked before. However now I keep getting the error message below when trying to refresh:
Last refresh failed: Tue Aug 14 2018 08:33:06 GMT+0800 (Singapore Standard Time)
There was an error when processing the data in the dataset.Hide details
| Data source error: | The command has been canceled.. The exception was raised by the IDbCommand interface. |
| Cluster URI: | WABI-WEST-US-redirect.analysis.windows.net |
| Activity ID: | 9712ab71-9fbe-4939-b630-2b57c28fd182 |
| Request ID: | fe788762-9ff6-484c-44ea-eedc6228eec1 |
| Time: | 2018-08-14 00:33:06Z |
my gateway is an on premise data gateway (not personal) version number: 14.16.6697 (May 2018).
can anyone highlight what this EDbCommand interface actually does and why is there an exception raised by this module?
Much thanks
5 Replies
From what I understand it is this:
https://msdn.microsoft.com/en-us/library/system.data.idbcommand(v=vs.110).aspx
or something similar at least.
I'd suggest using Power BI desktop and doing a manual refresh of the data model yourself. You should get a more detail explaination through there.
It is worth to check all your data queries are using the same format of setup especially using SQL as Data Source.
A max up setup will cause the exception of IDbCommand interface.
https://community.powerbi.com/t5/Report-Server/SCHEDULED-REFRESH-ERROR/m-p/724799#M10744
Hope this could solve your problem.
Hi,
I actually had the same case today. In my scenario removing filtering from KPI tile and from table resolved issue. Measure causing the problem was pretty simple build on direct query fact in the model.
consider disabling "fuzzy matching" when merging querries.
It appears that fuzzy matching is not compatible with refresh scheduling.
Disabling this feature will most probably result into fewer matches, so consider transforming your data/queries accordingly.I am not sure why this is happening. I too had this issue with multiple reports published in Premium capacity workspace and disabling fuzzy matching did the trick.
Hope this helps.
Hi,
Sorry to jump on your thread but we are currently receiving this error and it looks very similar with IDbcommand interface
Data source error: DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed:
OData Version: 3 and 4, Error: The remote server returned an error: (500) Internal Server Error. (Internal Server Error)
OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. (Internal Server Error)
OData Version: 3, Error: The remote server returned an error: (500) Internal Server Error. (Internal Server Error). DataSourceKind = OData. DataSourcePath = https://enwl-prod.api.saastagetik.com/basic/aih/data/v1/PROD_TGK_ENWL_006/001/Datasource_000001(). . The exception was raised by the IDbCommand interface. Table: SAP timesheet connector.
Cluster URI: WABI-UK-SOUTH-redirect.analysis.windows.net
Activity ID: 961ffae8-9156-4e3e-ad4a-4cdcdb6fdda3
Request ID: 5de6a4d7-412e-46dc-9f98-772a7d475640
Time: 2024-06-06 07:25:58Z
Anyone have any ideas how to resolve this as its really odd and only happens on a Wednesday??
Any help would or advice would be much appreciated.
Thanks,
Steve
