Named Pipe Error - Cant load data into Lakehouse

[AnthonyGenovese]

I have been trying to load a single table from on prem Sql Server to a newly created Lakehouse. The data loads fine from the gateway. We see a success message and data in the staging artifact.  However, the next step that writes the data to the Lakehouse fails everytime.  (Error Message and screen shots below). We have tried the following

1) Created a new Workspace & Lakehouse just in case something happened with the automatically created artifacts.

2) Removed all spaces and special characters from table and column names

3) Double checked all data types are correct

4) Tried multiple different tables, some with many rows, some with only 1 row.

5) We tried creating the dataflow from the Lakehouse & from the New Dropdown button in the workspace

6) We tried using the default destination connection and changing the destination connection.

7) We did try creating two data flows, one that is just a dataflow with no destination. And then a second that used that dataflow as a source and then created a destination. This actually worked. However, this seems horribly inefficient

Mashup Exception Error Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: 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) Details: DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;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);ErrorCode = -2146232060;Number = 53;Class = 20

[AnthonyGenovese · Accepted solution]

Issue was resolved after July 2023 gateway application was published and installed. 

[SidJay]

Thank you for letting us know. There were several reliability improvements in the July Gateway.

[SidJay]

As Miguel mentioned, these would be changes to the configuration of your firewall or proxy server.

[SidJay]

Is your Gateway server / proxy configured to allow the following?

• Protocol: TCP
• Endpoint: *.datawarehouse.pbidedicated.windows.net
• Port: 1433

If not, could you please see if applying those configuration settings resolves the issue?

Based on the error you shared as well as your point #7, it sounds like the Gateway server is unable to connect to the Warehouse instance that is used for compute against staged data.

Thanks

[AnthonyGenovese]

Still seeing the issue. Our IT department has confirmed that the firewall is open and they see data moving out. Any other suggestions? 

[AnthonyGenovese]

Where do I apply this configuration in the gateway application?

[miguel]

This would be configurations on your own network where the application is running as the application doesn't control such network settings at the environment level.