Forum Discussion
On-premise data gateway cannot connect to database
Hey Lorenz33 ,
Since Windows authentication works on the new Windows Server 2025 gateway cluster, the gateway itself is installed correctly and can reach the SQL Server. The issue is likely related to how SQL authentication (Basic authentication) is connecting. The error message about “Named Pipes Provider, error: 40” usually indicates a network or SQL configuration problem rather than a Power BI issue.
Most commonly, this happens when TCP/IP is not enabled on the SQL Server, the correct port (typically 1433) is blocked by a firewall, or the SQL Server Browser service is not running for a named instance. Windows Server 2025 may also have stricter firewall settings compared to 2016, which could explain why it works on the old gateway cluster but not the new one. Checking that TCP/IP is enabled in SQL Server Configuration Manager, confirming the correct port is open, and specifying the server name with the port number (for example, ServerName,1433) usually resolves this type of issue.
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!
Thanks Mohdzaid. The new Windows 2025 Server on-premise data gateway cluster is being tested with plans to replace the Windows 2016 Server on-premise data gateway cluster. With the Windows 2016, data gateway I am able to successfully create a connection to the same SQL Server database using basic authentication. As it works on the Windows 2016 data gateway and not the Windows 2025 data gateway, this should mean that the required port (1433) should already be open and that there are no firewall issues. Could the Windows 2025 data gateway be attempting access through a different port?
Hi Lorenz33
Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.The previous responses did not address my question. This was my reply to the previous responses:
The new Windows 2025 Server on-premise data gateway cluster is being tested with plans to replace the Windows 2016 Server on-premise data gateway cluster. With the Windows 2016, data gateway I am able to successfully create a connection to the same SQL Server database using basic authentication. As it works on the Windows 2016 data gateway and not the Windows 2025 data gateway, this should mean that the required port (1433) should already be open and that there are no firewall issues. Could the Windows 2025 data gateway be attempting access through a different port?Hi Lorenz33
In this scenario, since the same SQL Server connection works through the Windows Server 2016 gateway but fails with the Windows Server 2025 gateway, it indicates that the issue may be related to network configuration, security policies, or protocol behavior specific to the newer operating system.
At this point, it is difficult to confirm whether the problem is related to port access, firewall rules, or other OS-level changes introduced with Windows Server 2025.
Therefore, I recommend opening a Microsoft Fabric Support and Status | Microsoft Fabric with Microsoft so the support team can further investigate the gateway logs, network connectivity, and any potential compatibility or configuration differences with Windows Server 2025.