Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

[Jreyes85]

Starting 5/15/25 9:00 AM CST all of my Dataflow Gen2 and Semantic Models that connect to a Fabric Warehouse started failing with the following error message: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server), everything was working fine prior to this time.

[Jreyes85 · Accepted solution]

The issue when away on it's own, nothing done on my end (workspace), did not had to change any settings but I did open a ticket internally.

[burakkaragoz]

Hi @Jreyes85 ,

Eyvallah kanka, bağlantıdaki konuyu ve yorumları detaylıca inceledim. Kullanıcının yaşadığı hata şu şekilde:

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Bu hata genellikle ağ bağlantısı, SQL Server yapılandırması veya güvenlik duvarı gibi altyapı kaynaklı sorunlardan kaynaklanır. Forumda da Microsoft destek ekibi bu yönde bazı adımlar önermiş. İşte bu duruma uygun, sade ve doğal bir İngilizce cevap:

---

Hi @Jreyes85 ,

That error usually means the client can’t reach the SQL Server—either due to network issues or server config. Here are a few things to check:

• Make sure SQL Server allows remote connections.
• Check that the SQL Server Browser service is running.
• Ensure Named Pipes and TCP/IP protocols are enabled in SQL Server Configuration Manager.
• Verify that port 1433 is open and not blocked by a firewall.
• Try connecting using SQL Server Management Studio (SSMS) from the same machine to see if the issue is specific to Fabric or more general.

Also, if you're connecting from a local machine to a Fabric Warehouse SQL endpoint, make sure your network allows outbound traffic to that endpoint.

Here’s a helpful Microsoft doc for deeper troubleshooting:
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-t...

Let us know how it goes!

---

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

[v-pnaroju-msft]

Hi Jreyes85,

We have not received a response from you regarding the query and were following up to check if you have found a resolution. If you have identified a solution, we kindly request you to share it with the community, as it may be helpful to others facing a similar issue.

If you find the response helpful, please mark it as the accepted solution and provide kudos, as this will help other members with similar queries.

Thank you.

[v-pnaroju-msft]

Hi @Jreyes85,

Thank you for your inquiry through the Microsoft Fabric Community Forum.

Based on my understanding, the error you are encountering is typically indicative of a network or configuration issue.

Kindly follow the steps mentioned below, which may help in resolving the issue:

1. Verify the SQL Server configuration and ensure that remote connections are enabled. Also, confirm that the SQL Server Browser service is running and that Named Pipes and TCP/IP protocols are enabled.
2. Check the network settings to ensure that port 1433 is open and is not being blocked by any firewall.
3. Use SQL Server Management Studio (SSMS) from the same environment to test connectivity directly.

Additionally, please refer to the following link for further troubleshooting assistance:
A network-related or instance-specific error occurred - SQL Server | Microsoft Learn

If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members facing similar issues.

Should you have any further queries, please feel free to contact the Microsoft Fabric Community.

Thank you.

[josef78]

same error there, when connection to SQL endpoint of Warehouse from local computer