Error when extracting data from Microsoft 365 CRM to Power BI

[bobbity]

Hello, I am using dataverse to extract data from CRM into Power BI Power Query. For the past few weeks, there hasn't been any issues with establishing a connection and getting the data. However, just earlier this week, I have been unable to retrieve any sort of data; instead, I encounter the following error - 

DataSource.Error: 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.)
Details:
DataSourceKind=CommonDataService
DataSourcePath=*organization CRM web portal here*
Message=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.)
ErrorCode=-2146232060
Number=258
Class=20

________________________________________________________________________________________________________________________________________

As far as I know, there has not been any changes to my user privileges, or any changes to our servers.

[v-stephen-msft]

Hi @bobbity ,

For the 'DataSource.Error: Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the pre-login handshake.' error. I found some similar posts for you reference.

Unable to connect Power BI Desktop to Azure SQL Da... - Microsoft Power BI Community

SQL Connection error - Named Pipes - Microsoft Power BI Community

Solved: Error while connecting to SQL database after PBI l... - Microsoft Power BI Community

A connection was successfully established with the server, but then an error occurred during the pre...

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[bobbity]

Short update: By using my personal mobile hotspot, I was able to successfully retrieve all the data from CRM. However, when I swapped back to my office's WiFi, the error occurred again. Is there any way to troubleshoot or check what is the cause of the problem (which is likely my office's WiFi/Network)?