Dataflows Gen 2 Destination - Network-related error while establishing a connection to SQL Server

[Kwarre35]

Hello, 

I am not sure why I am receiving this error and what to do about it. Any documentation references or things to try would be much appreciated.

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) (Request ID: aac5e031-ef0d-4067-af54-a6c18dd8cd91, Region: us)

Details

Reason = DataSource.Error

DataSourceKind = Lakehouse

DataSourcePath = Lakehouse

DataSourceKind.2 = SQL

DataSourcePath.2 = xXxXxXMaskedxXXxXxXxXccxz7ndcexuvbtax3wv7opzby.datawarehouse.fabric.microsoft.com;TenantData

Message = 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 can preview my destination successfully, until I attempt to create the new table by hitting next:

I have write access to the Lakehouse: 

I have written other tables successfully from csv files from the folder in a lakehouse into delta tables, but I cannot seem to get the destination to work within a Dataflows Gen 2 to land a basic table successfully into a lakehouse table. 

I am a Power BI Admin for my company

I do not see anything explicitly in Microsoft Documentation that is obvious clue for me where to start

https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-data-destinations-and-managed-se...

[v-xianjtan-msft]

Hi @Kwarre35 

According to your description, Please check the following:

1. Ensure that the SQL Server instance is running.

2. Ensure that SQL Server is configured to allow remote connections.

3. Make sure the firewall is not blocking the SQL Server port (the default port is 1433).

Please refer to A network-related or instance-specific error occurred - SQL Server | Microsoft Learn get detailed steps.

Best Regards,
Jarvis Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Kwarre35]

Thanks for the lead. Will need to bring in additional resources to help me troubleshoot this. 

[GilbertQ]

Hi @Kwarre35 

Can you confirm if the lake house has been created with the new schema preview enabled? If the new schema preview is enabled, you will not be able to access the SQL endpoint for the time being, as this is currently still in preview.

But any work around for this is to create a new lake house, not in. there's not enabling the schema preview.

[Kwarre35]

Thanks @GilbertQ for the suggestion, but no dice. 

I created a new Lakehouse, left the new schema preview unchecked when creating. I tried landing the table into the new lakehouse and I got the same error message.