Forum Discussion
Unable to refresh dataflows - error occurred during the pre-login handshake
I have a number of dataflows, that pull views from Azure SQL Databases. Since 14th Jan 2023 they are failing at random spots during a scheduled refresh with the error message:
Microsoft SQL: A connection was successfully established with the server but then an error occurred during the pre-login handshake. (provider: SSL Provider error: 0 - The wait operation timed out.)
- The data source connection uses Oauth2 credentials and I have tried multiple times to reauthenticate.
- It spans across SQL Databases eg AzureSQLServer/DB1 AzureSQLServer/DB2 etc.
- I have checked on the Azure SQL Server that "Allow Azure services and resources to access this server" is ticked on the Networking tab.
- I have tried changing the data source and changing whether it is encrypted or not with no difference
The dataflow refreshes have been otherwise working fine with no changes.
If I create a brand new dataflow, and specify the same Azure SQL Database as the data source, it will browse the database server just fine, and allow me to select a table to include, and even show a preview of the data. But when I finish it up and refresh the feed, it fails. In this case I picked a tiny table with 7000 rows and it still failed.
Is anyone else experiencing this - or where do I begin to troubleshoot? Thank you.
Hi timb-0073 ,
Sorry I am late.
It a known issue.Engineers are working on repairs.I would update here as soon as possible if there is any update about it.
Best Regards
Community Support Team _ PollyIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
22 Replies
itchyeyeballsImpactful Individual
Seems like there are dataflow issues.
Our existing dataflows seem to be working ok, however when I create a new one it allows me to browse to the (on prem SQL server) DB table and view the data in preview but then fails when I save the dataflow and click refresh data.
Error is - Credentials are required to connect to the SQL source
Credentials are correct (it uses the saved credentials once I enter the basic database details)Australia
We had the exact same issue for our Australia hosted instance (no issues with our UK tenant). As with other comments this started working yesterday after mid-day UK time.
We also logged a ticket with Microsoft but have not had a response in the last 24 hours or so.
Is this a related issue, has anyone esle got similar problems:
For all existing dataflows in PPU workspace (referencing dataflows in other standard (pro) workspaces) refreshes have suddenly failed since at least Monday, 16.01.2023 (no problems up until 02.01.2023) . Creating new dataflows referencing dataflows in other standard (pro) workspaces in newly created PPU workspace is also not possible.
Hi timb-0073 ,
Sorry I am late.
It a known issue.Engineers are working on repairs.I would update here as soon as possible if there is any update about it.
Best Regards
Community Support Team _ PollyIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I can't understand why the issue wasn't posted to the PowerBI status page, unless I am missing something?
Sunny_ShekherMicrosoft Employee
Do we have any update on this. Few of us are still experiencing intermitent issue.
What happed that had triggered this issue.
Hello, I may have found the solution to the problem.
I had my credentials stored in my sharepoint connection inside the gateway, but when you create a new connection, it automatically enters the adress of the sharepoint site. You have to add a "/" at the end of this address for it to work again, I don't why.
If someone from Microsoft reads this, please send money and tickets Restau.
Yes - reocurred for us too this morning (20th Jan 2023)
We have seen the issue come back again with two more failed refreshes ☹️
Anyone seen the same? I've now put in a complaint with Microsoft about how our support case has been handled.
If anyone else has raised their issue with Microsoft and would be willing to share their support case numbers please post them here so I can share with MS.
Ours is 2301160050000773.
