Hi All,
I'm having a problem with a few reports today.
We used to report on Dynamics from an Azure SQL db fed from the CRM Export plugin, which has now deprecated. We altered the reports and hooked them up to the new TDS endpoint in dynamics where they have been refreshing just fine.
On Friday morning, I delete the old reporting SQL as its no longer required. This has caused some reports to stop refreshing, even though there was no reference to that database in the pbix. The error only mentions the TDS endpoint, but the only reports that are broken are the ones that used to use the old Azure database and now use TDS instead.
Creating a new report with TDS works just fine.
Any ideas?
Error as follows:
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: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Class","detail":{"type":1,"value":"20"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SQL"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"t****p.crm*.dynamics.com;**sandbox"}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2146232060"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"}},{"code":"Microsoft.Data.Mashup.ValueError.Number","detail":{"type":1,"value":"53"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: Project Tracker.
Cluster URIWABI-NORTH-EUROPE-D-PRIMARY-redirect.analysis.windows.net
Activity IDf9e5a7d9-c142-4cbf-9bab-7c2d09aca880
Request ID7b2a735f-5550-eb59-7393-f1484e69e314
Time2023-08-17 12:29:36Z
