Error trying to retrieve table from a dataflow Gen2

[XCT]

Hi,

I've this message when I'm trying to retrieve data from a dataflow Gen2 in Premium capacity with Power BI desktop.

Details: "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)"

I've enabled the staging in my dataflow...I used the right dataflow connector in Power BI desktop...

I'have the same error when I try to connect Power BI desktop to the SQL EndPoint of a Fabric Warehouse...

Need help!

[XCT · Accepted solution]

Hi everyone!

It’s definitely a firewall configuration issue on my company’s network. For your information, it works perfectly from home.

PBI Desktop directly queries the SQLAnalytics endpoint (Azure SQL Server TDS endpoint), by default through port 1433. Our corporate network policies block this traffic. Therefore, we need to consider a workaround if we want to roll out Fabric to other users, as the same applies to SQL connections to both Fabric Warehouse and Lakehouse.

We found this documentation here => https://learn.microsoft.com/en-us/fabric/database/sql/connect

Regards,

XCT

[v-lgarikapat]

@XCT ,

Thank you for reaching out to the Microsoft Fabric community forum.

@Shahid12523 , @MohamedFowzan1   Thank you both for your prompt responses.

 @XCT In addition to the inputs shared by @Shahid12523  and @MohamedFowzan1 , I’ve also added the previously resolved threads here. They may help you better understand the issue and work toward a resolution.

Solved: Power bi connect to dataflow gen2 - Microsoft Fabric Community

Solved: PBI Desktop - Unable to connect to Dataflow Gen2, ... - Microsoft Fabric Community

Solved: Power bi connect to dataflow gen2 - Microsoft Fabric Community

We appreciate your engagement and thank you for being an active part of the community.

Best regards,
Lakshmi.

[Shahid12523]

Use TCP/IP, not Named Pipes — add tcp: before the SQL endpoint.
Check network access — firewall, VPN, or proxy might be blocking it.
Verify endpoint URL — make sure it's correct and reachable.
Use the right connector — Dataflow Gen2 needs the Dataflow connector, not SQL Server.
Ensure staging is enabled and run — data must be staged before querying.

[MohamedFowzan1]

Hi @XCT 

Looks like you would just have to go through all the setup and this doesnot seem to be an actual limitation or blocker:

1. Verify Endpoint Details

   • Ensure you are using the exact SQL endpoint URL or instance name provided for your Dataflow Gen2 or Fabric Warehouse.

2. Check Network Connectivity

   • Try to ping the endpoint or test connection from your machine. If you cannot reach it, network/firewall rules are likely blocking access.

3. Review SQL Server Configuration

   • Make sure that remote connections are enabled and that the needed protocols (TCP/IP, Named Pipes) are active.

4. Check Firewall Settings

   • On the server/network, make sure the ports used for SQL Server (typically 1433) are not blocked.

5. Update Power BI Desktop

   • Ensure you’re running the latest version of Power BI Desktop and that your connectors are up to date.

6. Validate Staging and Premium Capacity

   • Confirm that staging is properly enabled and that your Power BI workspace has the necessary Premium capacity.

7. Test from Another Network or Machine

   • Sometimes local network issues cause problems. If possible, test from another machine or network.

When Using Fabric Warehouses

• Ensure you’re connecting to the SQL endpoint specified for the Fabric Warehouse and that the warehouse is online and accessible in the Power BI service.