Forum Discussion
Trouble with refresh : Unable to connect to data source undefined
Hi guys,
I'm trying to refresh a dataset from 7 data sources - three of them are databases from the IBM Informix Pronto dataset and the other four are local files.
I suddenly got this error 2 weeks ago (see below). I've checked that my power bi desktop data source privacy level is the same to power bi web service; on-premise gateway (personal mode) is updated to the latest version and online; data files' names are correct.
Does anyone have any ideas or the same experience? Really appreciate
Failed | Unable to connect to the data source undefined. |
Underlying error code: | -2147467259 Table: TABLEXXX. |
Underlying error message: | Microsoft Informix Client: Statement interrupted by user. SQLSTATE=IX000 SQLCODE=-213 |
DM_ErrorDetailNameCode_UnderlyingHResult: | -2147467259 |
Microsoft.Data.Mashup.ValueError.DataSourceKind: | Informix |
Microsoft.Data.Mashup.ValueError.DataSourcePath: | XXXX;XXXX |
Microsoft.Data.Mashup.ValueError.ErrorCode: | 0 |
Microsoft.Data.Mashup.ValueError.Message: | Statement interrupted by user. SQLSTATE=IX000 SQLCODE=-213 |
Microsoft.Data.Mashup.ValueError.Reason: | DataSource.Error |
Cluster URI: | WABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net |
Activity ID: | e8c8e80f-0c45-4b32-8bd8-ae80b1032f1c |
Request ID: | 7c112733-1098-d915-666c-663b34332553 |
Time: | 2019-10-29 01:58:18Z |
I finally solved this problem!!! I did a research about SQL ERROR -213 and it is about query timeout. Then I set a time out option in my data source. ( [timeout=#duration(0,0,30,0)])), then the problem solved! But it took so long to refresh the dataset now.
2 Replies
venalMemorable Member
-213 Statement interrupted by user. The database server received an interrupt signal from the user, probably because the user pressed the interrupt key (usually Delete or Control-C). The statement ended early. A program should roll back the current transaction and terminate gracefully. If the statement could modify a table, an interactive user should execute the ROLLBACK WORK statement to remove any partial modifications.
There was some known issues also going on, please refer the link.
If your issue is not in known issues list, please try to refresh the report from desktop and save the file with different name, publish and try to re-pro the issue.
Note:- Try to maintain the latest versions. (Power BI Desktop, On-premises Data Gateway).
If this post helps, then please consider Accept it as the solution to help the other members find it more
If this post was helpful may I ask you to mark it as solution and give it some kudos?
I finally solved this problem!!! I did a research about SQL ERROR -213 and it is about query timeout. Then I set a time out option in my data source. ( [timeout=#duration(0,0,30,0)])), then the problem solved! But it took so long to refresh the dataset now.