Connection to Lakehouse tables in Power BI Desktop gives a login error

[PowerNewUser]

When I try to connect to a lakehouse table using the SQL endpoint, I get the following error

Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The specified network name is no longer available

Any suggestions? Am trying to pull a lakehouse table into a separate workspace through import. Tried both Microsoft Credentials + Windows Credentials. I also tried to follow Fabric Query to PowerBI - YouTube - when I download the visual query linked pbix - it does not open and gives an error. 

[PowerNewUser · Accepted solution]

Update : the issue turned out to be our firewall on the desktop. Still working on getting it resolved. Without it was able to connect to the sql endpoint. 
Temporary work around: Created a data flow in the dowstream workspace to pull data from the lakehouse. Next pulled the dataflow into power bi desktop. 

[Anonymous]

Hi @PowerNewUser ，

The error message indicating an issue with the SSL Provider suggests there might be a problem with the network connection or the configuration of the SQL endpoint you're trying to use. Given that you're attempting to connect using the SQL endpoint, it's crucial to ensure that the endpoint is correctly configured and accessible.

Here are a few steps you can take to troubleshoot and hopefully resolve the issue:

• Verify Network Connectivity: Ensure that your network connection is stable and that the SQL endpoint is reachable from your machine. You can do this by pinging the endpoint from the command line.
• Check Endpoint Configuration: Review the configuration of your SQL endpoint to ensure it's set up correctly for external access. This includes checking firewall rules and SSL settings.
• Permissions Check: Confirm that the credentials you're using have the appropriate permissions to access the lakehouse table. This might require coordinating with your database or lakehouse administrator.

Since you're working with lakehouse tables, consider using Power BI's Direct Lake mode for connecting to your lakehouse. This method bypasses the need for a SQL endpoint and might provide a more straightforward connection path. For detailed steps on connecting to a lakehouse table in Power BI using Direct Lake mode, please refer to the official documentation here: Direct Lake Overview.

Best Regards,

Xianda Tang

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

[Element115]

@Anonymous   @PowerNewUser Unfortunately, POwer BI DirectLake mode is only available with Power Bi Service and not Power BI Desktop, which leads to a further annoyance.  If you have a report that uses field parameters, which is a feature only available to Power BI Desktop, then you can't port this report to Power BI Service because you will lose the field parameters.  

So this is not really a solution as long as feature parity between Power BI Desktop and Service has not been achieved.

[PowerNewUser]

I can pull in files using the direct query option from the lakehouse in the power bi get data. I get the same error if I say connect with sql endpoint.  Problem is I need to import as I need to transform(filter and add another source) it prior to consuming it in my report.