Interesting SSL error

Hi TylerFCG 
Thank you for being part of the Microsoft Fabric Community.
The message indicates that SSL cannot be enabled when connecting to a server that does not have SSL enabled. If the server has SSL enabled, ensure that the minimum required SSL protocol (TLS 1.2 or later) is correctly configured.
Enable/Check SSL Configuration:
Make sure that SSL is enabled on your Databricks cluster.

• If it is disabled, try modifying your Power BI connection settings:
  • Go to Data source settings in Power BI.
  • Check Encryption settings and match them with Databricks requirements.
  • Try explicitly disabling SSL in the connection string if necessary.

Use DirectQuery Instead of Import Mode

• Since Import Mode pulls large result sets into Power BI, switching to DirectQuery can reduce the load by querying Databricks on demand.
  • In Power BI, go to Transform Data → Change data source mode to DirectQuery.

If the above information helps you, please give us a Kudos and marked the reply Accept as a Solution.

Thanks,
Cheri Srikanth

Hi TylerFCG 

The error you are encountering in Power BI when connecting through a VPN gateway to Databricks appears to be related to data size, query execution time, and SSL/TLS configuration. Since smaller queries work fine while larger ones fail, it suggests that Power BI is struggling to handle the retrieval of large datasets from Databricks. The error message indicates that Power BI encounters a retriable error while attempting to download result files from Databricks' cloud store, and after multiple retries, it fails. This could be due to timeout limits, network constraints, or gateway processing limitations. Additionally, the error mentions an SSL/TLS mismatch, meaning that either the VPN gateway, Power BI, or Databricks may not be aligned on the required security protocols (TLS 1.2 or higher). To resolve this, you can try optimizing your queries to reduce the data size being imported, increasing timeout settings in Power BI and Databricks, verifying SSL/TLS configurations, and checking Databricks' query logs for failures. Another potential solution is switching from Import mode to DirectQuery mode, as this would allow Power BI to query Databricks dynamically without loading large datasets into memory. Lastly, testing outside the VPN may help determine if the issue is related to the network configuration rather than Power BI or Databricks itself.