Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Grow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.

Reply
cmeu
Advocate III
Advocate III

Dataset refresh utilizing powerplatform.dataflows connector fails with error cannot connect to SQL

We use dataflows extensively in our environment for data prep - this weekend we began receiving errors like this for many of our datasets:

DataSource.Error: <ccon>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). DataSourceKind = PowerPlatformDataflows. DataSourcePath = PowerPlatformDataflows. 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. </ccon>. The exception was raised by the IDbCommand interface. Table: FiscalCalendar.Cluster URI:WABI-US-EAST2-redirect.analysis.windows.netActivity ID:2a9dc999-23d6-4167-8875-0a44f80c3d48Request ID:e1302210-abeb-c7c4-a7a5-4c0e8c32bd06Time:2023-05-08 22:47:22Z

 

Anyone have an idea what to do? We're not connecting to a SQL server here, it looks like the connector isn't working..

1 ACCEPTED SOLUTION
cmeu
Advocate III
Advocate III

Looks like this may be related to a temporary system issue. The workaround shared there, was to: turn off enhanced compute for the affected dataflow. This has indeed helped avoid this issue - at the cost of query folding.

Hope they can get it resolved quickly - thanks for guidance posted at support site!

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Same issue, but with a DataSet... Hope it gets fixed soon

cmeu
Advocate III
Advocate III

Looks like this may be related to a temporary system issue. The workaround shared there, was to: turn off enhanced compute for the affected dataflow. This has indeed helped avoid this issue - at the cost of query folding.

Hope they can get it resolved quickly - thanks for guidance posted at support site!

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

Power BI Carousel June 2024

Power BI Monthly Update - June 2024

Check out the June 2024 Power BI update to learn about new features.

RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.

Top Solution Authors