A network-related or instance-specific error occurred while establishing a connection to SQL Server.

[SS_Analyst]

Hello Microsoft Community,

I'm working on setting up a gateway to my Fabric Lakehouse. Using Power BI desktop, I can access the data directly without issues. However, due to the drawbacks of importing data in this manner, such as the absence of a date hierarchy, I've opted to import the data directly into Power BI.

To accomplish this, I follow the same steps as I would for a direct connection to the Lakehouse, but instead of selecting "Connect," I choose "Connect to SQL Endpoint." However, when I do this, I encounter the following error:

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 would highly appreciate it if anyone could assist me with this issue. 

Best regards.

[lbendlin]

This might be your issue:  On-premises data gateway considerations for data destinations in Dataflow Gen2 - Microsoft Fabric | ...

[SS_Analyst]

Thanks for the kind reply. I couldn't figure out how this could be relevant. I am not using Dataflow Gen2 in my Fabric data flow. Also my data is already in a lakehouse and I am trying to connect it to Power BI. If it was a firewall issue I should've had the issue when connecting directly using OneLake data hub direct method. The issue only rises when I try to use the SQL Analytics Endpoint of the same Lakehouse. 

[Anonymous]

Hi @SS_Analyst ,

Base on your description, it seems like it got error when connect to SQL Endpoint. Could you please check and verify the following info?

1. Enable remote connections

2. Verify SQL Server Network Configuration

TCP/IP Settings in SQL Configuration Manager 

3. Check SQL Server Browser Service is running

4. Configure Windows Firewall

How To: Configure Windows Firewall for SQL Server 

Best Regards

[SS_Analyst]

Hello again, 

Thanks for the kind reply! Unfortunately I don't think this can help me either. I am not connecting to SQL data base that I admin, but Microsoft Fabric data lakehouse SQL endpoint. There is absolutely nothing to configure and as I said in my previous comment if I connect directly to the lakehouse there is no problem. The problem rises when I am using the SQL Analytics Endpoint of the lakehouse. 

[ccmiller10]

Did you ever figure out the issue/solution for this? I'm running into the same thing after it was working perfectly fine for months.

[lbendlin]

i still think that the blockage on port 1433 for these endpoints is the cause.