topic Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL in Dataflow

Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

SuperFietsAGTT — Mon, 25 Nov 2024 13:44:38 GMT

Hi all,

For some reason, I am getting the following error message for basically all my Dataflow Gen2's which worked perfectly before:

xf3_hashtotals_WriteToDataDestination: There was a problem refreshing the dataflow: 'Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.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: Reason = DataSource.Error;ErrorCode = 10478;DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;DataSourceKind.2 = SQL;DataSourcePath.2 = et4kwdqlipiuxcesfmyol3mrfe-4chdtikxiiru7jh6yts7jwqa3a.datawarehouse.fabric.microsoft.com;lh_loader;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;State = 0;Microsoft.Data.Mashup.Error.Context = User'. Error code: Mashup Exception Data Source Error. (Request ID: 02f4c2c1-e158-49c7-bc41-eb24ed47de25).

The Dataflow Gen2's read files from the OneLake storage of the connected lakehouse. Everything worked perfectly last week, but today I am getting this error. For some reason some queries do load, others don't. And it is random each time, so the next time the other query that errored runs and the other that worked before now shows the error.

As far as I am aware nothing has changed, I am the admin.

We aren't using any gateway's whatsoever, so adding a port to the firewall probably isn't going to fix anything. That's the only thing I could find online for this error: (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server.

Also after trying a few times two other dataflows won't even publish and give the following error message: Unexpected error occurred while creating your data destination. Please try again later.

Guess everything is broken lol... Hopefully someone can help!

PS: Even when loading empty queries, without any data. It gives certain errors.

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

AdeV-Oly — Mon, 25 Nov 2024 15:14:18 GMT

Same issue as in https://community.fabric.microsoft.com/t5/Data-Warehouse/The-server-was-not-found-or-was-not-accessible/m-p/4299971

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

AdeV-Oly — Mon, 25 Nov 2024 15:39:14 GMT

Temporary solution: click on 'Refresh now'. Might take an attempt or two.

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

Timbaaaal — Mon, 25 Nov 2024 16:08:47 GMT

This work for my dataflow which doesnt have too much queries but not for the bigger one (9+ queries) as there is always one that randomly fail..

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

SuperFietsAGTT — Mon, 25 Nov 2024 16:16:49 GMT

Exact same behaviour for me

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

CSF — Mon, 25 Nov 2024 20:24:47 GMT

this could be related... Microsoft 365 down? Current problems and outages | Downdetector

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

Stinkys — Tue, 26 Nov 2024 00:07:34 GMT

I have been experiencing this problem for 2 days now. Everything was working fine on Friday PM, haven't made any changes to Dataflow G2 process but now it is failing to refresh and and I can't republish. The UI in DFG2 is also running extremely poorly and taking minutes to show the output on something that was taking seconds previously.

Have tried removing and recreating the destination config. Pretty big effort to recreate the entire flow, especially if it's all for nothing.

The errors appear to bounce from source/destination, and across multiple tables (but not all of them). The connection appears to test OK. Sometimes I can expand other Lakehouse and view their tables, sometimes it times out while retrieving the tables.

Something feels fundamentally broken. If only there were a way to log a ticket with M$

DataSource.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) (Request ID: 6ad01736-6981-4361-a199-e5b3dda81a94, Region: australia)DetailsReason = DataSource.Error ErrorCode = 10478 DataSourceKind = Lakehouse DataSourcePath = Lakehouse DataSourceKind.2 = SQL DataSourcePath.2 = gpb4ryg32e7ubbboy33snqenza-t3qxhdfsle6e5kcmss4ftryy2y.datawarehouse.fabric.microsoft.com;BronzeHouse 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 State = 0

Error number 53 hmm... reminds me of the age old proverb...

It's not DNS

There's no way it's DNS

It was DNS

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

Stinkys — Tue, 26 Nov 2024 03:41:59 GMT

Looks like we're back online!

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

Timbaaaal — Tue, 26 Nov 2024 07:46:48 GMT

Yes, working on my end too!

Re: Error: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL

CSF — Tue, 26 Nov 2024 13:56:33 GMT

All good over here as well today.