Forum Discussion

Allisond's avatar
Allisond
Advocate II
5 years ago
Solved

Reports stopped refreshing: Pre-login Handshake Error

Hello!  I am getting this error when I try to refresh existing reports connected to an external db with Windows credentials.  They were working fine 2 days ago and I have not adjusted any of my setti...
Need Help
  • v-yingjl's avatar
    v-yingjl
    5 years ago

    Update:

    Engineers are working on a fix which will be included in the October versions of Power BI Desktop and Gateway due to be released by 10/17/2020.

     

    Best Regards,
    Yingjie Li

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

v-yingjl's avatar
v-yingjl
Community Support
5 years ago

Hi Allisond ,

Which version of SQL Server are you using to connect to power bi? Please check your power bi desktop version is the latest 2.85.681.0 64-bit (September 2020). Currently this version of power bi desktop seems have a known issue when connecting to SQL Server 2019. If your desktop version is updated to this version automatically and the SQL version is SQL server 2019, it could cause this issue.

You can try to use the previous version of power bi desktop like Aug 2020 temporarily to wait for the version fix. 

 

In addition, you can also check that  if you have added the TCP port and UDP port(1434) in the inbound rule of the Windows Firewall, and you can verify TCP port in SQL Server Configuration Manager.
For more details about configuring remote access for SQL Server, please review the following blog.
https://blog.citrix24.com/configure-sql-express-to-accept-remote-connections/ 

 

 

Best Regards,
Yingjie Li

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

caseycook's avatar
caseycook
Helper I
5 years ago

It's not just SQL 2019.  We are using SQL 2016 and having the same issue.  Re-configuring the sql server to not force encryption seems to resolve the problem (not a great solution though).  Also, it appears that you can update your data sources to use your domain as part of the server name (e.g. servername.domain.com).  However, this is a lot of work.  Especially, since in the on-prem gateway you can't modify and esisting data source.  You have to create a net-new one.

Have not tried rolling back to a previous version of the gateway/desktop, but that could be a stop gap while you update all the connections.

If only M.S. would allow us to TrustServerCertificate=true, but I guess that's giving us too much power.