Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi all,
Today i'm having a dataflow constantly error and unable to publish/refresh
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
Some background information is i'm using an On Premise data gateway and then chaining the loading of the dataflow, to a pushing of the first data flow to a lakehouse (one of the workarounds from microsoft) as I don't have access to the data gateway.
This has worked for a few months without issued but suddenly started failing over the weekend. I have been unable to fix this even with creating a new dataflow to push the data to the lakehouse
any help would be appreciated
Solved! Go to Solution.
The issue is solved, was due to microsoft having a failure in the dataflowsgen2, there was a reddit post about it as many people across regions were having the same issues
The issue is solved, was due to microsoft having a failure in the dataflowsgen2, there was a reddit post about it as many people across regions were having the same issues
Hi @Marc_D
Here are some steps to troubleshoot and resolve the issue:
1.Ensure the SQL Server instance is up and running and that the instance name is correct.
2.Verify that remote connections are enabled on the SQL Server. Use SQL Server Management Studio (SSMS) or a similar tool to try connecting to the server using the same credentials and connection string as in your Dataflow.
3.If SQL Server is behind a firewall, confirm that the required ports (default: ’1433‘) are open.
4.Ensure the gateway is online and running. You can check this in the Power BI Service > Manage Gateways.
5.Update the gateway to the latest version if it’s outdated.
6.Navigate to Manage Gateway > Select your gateway > Test the data source connections.
Best Regards,
Jayleny
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 49 | |
| 18 | |
| 11 | |
| 10 | |
| 10 |