Forum Discussion
Mashup error - TDS/SQL
- Anonymous3 years ago
Hi andygill ,
It seems that the error you’re getting is related to the connection to the SQL Server that hosts the TDS endpoint.
this error can be caused by various factors, such as:
- The SQL Server name or instance name is incorrect or not reachable.
- The connection string or authentication settings for the TDS endpoint in Dynamics.
- The SQL Server is not configured to allow remote connections.
- The gateway is outdated or not selected for the dataset.
Solution:
- Verify that the SQL Server name and instance name are correct and match the ones in Power BI Desktop.
- Checking the connection string and authentication settings for the TDS endpoint in Dynamics to make sure they are still correct and up-to-date. You could also try recreating the connection to the TDS endpoint in the Power BI report to see if that resolves the issue.
- Open the port used by the SQL Server (default is 1433) in the firewall settings.
- Install the latest version of the gateway and make sure it is selected for the dataset in Power BI service.
Solved: SQL Server Named Pipes Provider, error: 40 - Microsoft Fabric Community
If in doubt, please do not hesitate to ask.
Best Regards
Community Support Team _ RongtieIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi andygill ,
It seems that the error you’re getting is related to the connection to the SQL Server that hosts the TDS endpoint.
this error can be caused by various factors, such as:
- The SQL Server name or instance name is incorrect or not reachable.
- The connection string or authentication settings for the TDS endpoint in Dynamics.
- The SQL Server is not configured to allow remote connections.
- The gateway is outdated or not selected for the dataset.
Solution:
- Verify that the SQL Server name and instance name are correct and match the ones in Power BI Desktop.
- Checking the connection string and authentication settings for the TDS endpoint in Dynamics to make sure they are still correct and up-to-date. You could also try recreating the connection to the TDS endpoint in the Power BI report to see if that resolves the issue.
- Open the port used by the SQL Server (default is 1433) in the firewall settings.
- Install the latest version of the gateway and make sure it is selected for the dataset in Power BI service.
Solved: SQL Server Named Pipes Provider, error: 40 - Microsoft Fabric Community
If in doubt, please do not hesitate to ask.
Best Regards
Community Support Team _ Rongtie
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.