Issue - Scheduled refresh failures

[Arvind07]

Hello
Recently we have been receiving frequent failures on datasets, the most frequent error is a schedule refresh specifically to the source Teradata. The gateways are connected successfully using a service account. For the Teradata error, the Teradata DBA says issue is not from a Teradata aspect. We have logged into Teradata with the service account and have intermittent issues doing so, ultimately able to log in successfully. The 2nd error is for a SQL server which has started popping up more frequently... These are the 2 errors:

Teradata Error:

Refresh failed:

__________ has failed to refresh.
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.
{"error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","pbi.error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<pi>The credentials provided for the Teradata source are invalid. (Source at td_prd.)</pi>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"Teradata"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"________"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessUnauthorized"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"Teradata\",\"path\":\"______\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessUnauthorized"}}],"exceptionCulprit":1}}} Table: PIN_View_Reset_Combined.
Next refresh for __________ is scheduled for June 8, 2020 11:00 UTC.

SQL Error:

Refresh failed:

__________ has failed to refresh.
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.
{"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":"<pi>Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</pi>"}},{"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":"__________________;__________________"}},{"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: _____________.
Next refresh for __________ is scheduled for June 8, 2020 23:00 UTC.

[v-yuta-msft]

@Arvind07 ,

I would suggest you create a support ticket here.

 

Regards,

Jimmy Tao

Regards,

Jimmy Tao

[PBILover]

I faced the same issue and opened a support ticket .

waiting for microsoft reply.

@Arvind07  Did you find any solution?

[Arvind07]

Thank you for the feedback, i will raise a support ticket.

@PBILover , nope, no solution 😞 

Did you get any feedback yet from your side after opening a ticket?

[PBILover]

we are still working on it. 😞

[Phoebe_Zhang]

i am facing the same issue... do you get any feeback?

[im_newbie_123]

Facing similar issue from past few days. 

The daily scheduled refresh fails.

Something went wrong
There was an error when processing the data in the dataset.
Please try again later or contact support. If you contact support, please provide these details.
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","pbi.error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Credentials are required to connect to the SQL source. (Source at raproddbsz01.database.windows.net;sz.)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"SQL"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"raproddbsz01.database.windows.net;sz"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceReference","detail":{"type":1,"value":"{\"protocol\":\"tds\",\"address\":{\"server\":\"ra*******.database.windows.net\",\"database\":\"sz\"},\"authentication\":null,\"query\":null}"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"CredentialMissing"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"SQL\",\"path\":\"ra*******.database.windows.net;sz\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"CredentialMissing"}}],"exceptionCulprit":1}}} Table: Employment History SaleOps Format.
Activity ID: 7cb1eda8-90e7-46e1-84bf-aebf0d98d3ee
Request ID: 58b926b6-06b2-46ca-9227-17c78004537e
Time: 2020-06-12 10:34:01Z

The data model updates properly when refreshed from PowerBI desktop.