Forum Discussion
Failed to refresh
Hi team, my report keep failed when refresh since June 9th till now.
Here is the detail, any suggestion what should I do? Thank you in advance!
| Data source error: | {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Class","detail":{"type":1,"value":"11"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SQL"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"stcvm-a27;TTS_Usage_Start_2018"}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2146232060"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding."}},{"code":"Microsoft.Data.Mashup.ValueError.Number","detail":{"type":1,"value":"-2"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: DistinctOneDay. |
| Cluster URI: | DF-MSIT-SCUS-redirect.analysis.windows.net |
| Activity ID: | 4ce3bd16-9f6f-4d2e-8a66-2b7809b5ef4b |
| Request ID: | de1705ad-22b8-1950-4e03-7b2188360079 |
| Time: | 2021-06-16 04:09:32Z |
5 Replies
- collinqSuper User
Hi garfieldhe ,
We had this problem recently as well and the resolution was that we had to upgrade the gateway.
- v-luwang-msftCommunity Support
Hi garfieldhe ,
1. On the Power BI side, you could set timeout option and check again. The maximum is 2 hours.
2. On the SQL side, you could use SSMS to check if there is a lock on one or more tables.
If your data is large, you could create views to optimize data size.
It is recommended to update the Connection Timeout and Command Timeout parameters in the relational Target Connection.
Best Regards
Lucien
- v-luwang-msftCommunity Support
Hi garfieldhe ,
Has your problem been solved, if so, please consider Accept a correct reply as the solution or share your own solution to help others find it.Best Regards
Lucien - collinqSuper User