Forum Discussion
Pre-Login Handshake Error with Dataverse as data source
Hi all,
when I want to create a new Dataverse data source in PBI desktop, I get the following error (see screenshot below)
DataSource.Error: Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - Der angegebene Netzwerkname ist nicht mehr verfügbar.)
Details:
DataSourceKind=CommonDataService
DataSourcePath=eoscrm.crm4.dynamics.com
Message=A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - Der angegebene Netzwerkname ist nicht mehr verfügbar.)
ErrorCode=-2146232060
Number=64
Class=20
The error occurs with different version of PBI desktop and different users, and with all our environments.
Searching the forum, I came across similiar issues with SQL Server but not with Dataverse - so all possible solutions didn't apply here.
Any ideas? Thanks and best regards, Ihno
7 Replies
We had the same error (in PBI Desktop, Excel and SSMS) which was hard to pinpoint, since occasionally at least listing tables from a dataverse environment did work. Finally it turned out that the firewall (ZScaler) did block certain SSL-encrypted network traffic due to a false packet inspection security alerts. Solution was to generally disable deep packet inspection for the traffic on ports 1433 & 5558 to the hostnames/IPs for the according dataverse environment.
Hi, IhnoHanuschka
It seems not a Power BI or Power Query issue.
It may be just transient errors, please try again after clearing credentials and cache.
Best Regards,
Community Support Team _ EasonThanks, v-easonf-msft ! Before posting here, I had cleared all Connections so that I had to log in again.
However, I didn't clear caches as I have no clue which cache to clear and how to do that... Can you give me a hint?Hello, was this issue solved?
Hi mcguija , currently, we don't use that report any more, I think it started to work again but don't remember well.
So - I can't give any details, sorry... 🤷♂️
