Forum Discussion
DataSource.Error: ErrorCode=-2146232060 Number=64 Class=20 State=0
Everything worked well three days ago. I switched off the pc, we went to the holidays for three days and back in the office I see this on power bi. I can't proceed with refresh:
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 - The specified network name is no longer available.)
Details:
DataSourceKind=SQL
DataSourcePath=10.10.50.50;SAP_IF
Message=A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
ErrorCode=-2146232060
Number=64
Class=20
State=0
I sincerely appreciate all the responds and tips. Somehow the problem was caused by this DBSafeer Agent. It automatically turned off during the holidays when my pc was swithed off. When I came back to office and tried to refresh the Power BI Desktop data it did not proceed because this DBSafer Agent was off. With it on everything went soothly.
4 Replies
Hi mamedoff_korea - similar error thread. please check the below links:
Solved: A connection was successfully established with the... - Microsoft Fabric Community
PowerBI Desktop - ErrorCode=-2146232060 - Microsoft Fabric Communitytry connecting to the SQL server using the same credentials and connection details. This can help determine if the issue is specific to Power BI or the server itself.If SSMS throws a similar error, it confirms that the issue lies with the network or SQL server configuration.
Hope it helps
I sincerely appreciate all the responds and tips. Somehow the problem was caused by this DBSafeer Agent. It automatically turned off during the holidays when my pc was swithed off. When I came back to office and tried to refresh the Power BI Desktop data it did not proceed because this DBSafer Agent was off. With it on everything went soothly.
Hi mamedoff_korea ,
Whether the advice given by rajendraongole1 has solved your confusion, if the problem has been solved you can mark the reply for the standard answer to help the other members find it more quickly. If not, please point it out.
Best Regards,
Neeko Tang
I have the same issue.
However, Friday i had to work from home and guess what? I could connect. So the issue is perhaps not always related to SQL servers but firewalls? Back at work today and still experimenting same problem. No changes have been made to our firewalls as per IT so waiting to see what they find.
