Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
nirupamroy
Frequent Visitor

Azure Databricks - Refresh Error

Hi

 

Need your help. Facing a strange issue while updating power bi dashboard connected to Azure Databricks while refreshing dataset. The dashboard was working absolutely find and was getting updated without any issue. But for the last couple of days receiving an error message, which is weird and unable to understand the exact issue. This is the error message I am getting in Power BI

Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: [DataSource.Error] ERROR [HY000] [Microsoft][Hardy] (35) Error from server: error code: '0' error message: '[Microsoft][Hardy] (134) File 73312b68-3741-47c9-8b45-92e8810a5795: A retriable error occurred while attempting to download a result file from the cloud store but the retry limit had been exceeded. Error Detail: File 73312b68-3741-47c9-8b45-92e8810a5795: An error had occurred while attempting to download the result file.The error is: [Microsoft][DSI] An error occurred while attempting to retrieve the error message for key 'DSSslErrorMessage' with message parameters [' -The revocation status of the certificate or one of the certificates in the certificate chain is unknown. -The certificate chain is not complete. -The revocation status of the certificate or one of the certificates in the certificate chain is either offline or stale.'] and component ID 110: Could not open error message files - Check that "C:\Program Files\Microsoft Power BI Desktop\bin\ODBC Drivers\Simba Spark ODBC Driver\en-US\DSMessages.xml" or "C:\Program Files\Microsoft Power BI Desktop\bin\ODBC Drivers\Simba Spark ODBC Driver\DSMessages_en-US.xml" exists and are accessible.. Since the connection has been configured to consider all result file download as retriable errors, we will attempt to retry the download.'.. '.
 

 

Any solution will be highly appreaciated. 
Thanks in advance.

 

Roy

6 REPLIES 6
v-pnaroju-msft
Community Support
Community Support

Hi nirupamroy,

We sincerely appreciate your inquiry via the Microsoft Fabric Community Forum.

From my understanding, the error you are encountering arises due to a certificate chain validation failure while attempting to download result files from Azure Databricks. This issue generally occurs when the SSL certificate is incomplete or untrusted, the Certificate Revocation List (CRL) or Online Certificate Status Protocol (OCSP) checks fail due to being unreachable, or if the ODBC driver files are missing or corrupted.

Kindly follow the steps outlined below, which may help to resolve the issue:

  1. Update the Simba Spark ODBC Driver by installing the latest version to address connectivity and SSL-related issues.
  2. Verify the certificate chain by accessing Databricks in a web browser. Click on the lock icon and ensure that no certificates are missing or untrusted.
  3. Ensure that your network or proxy allows outbound access to certificate validation endpoints (such as ocsp.* and crl.*).
  4. Reinstall the driver if the DSMessages.xml file is missing or corrupted.
  5. In the ODBC settings, add the parameter CheckCertRevocation=0 under advanced options. Please use this only for troubleshooting purposes and not in a production environment.
  6. Delete and reconfigure the Databricks connection in Power BI Desktop, and then re-enter your credentials.

Additionally, please refer to the following links for more information:
Connect Power BI to Azure Databricks - Azure Databricks | Microsoft Learn
Program Requirements - Microsoft Trusted Root Program | Microsoft Learn

If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members facing similar queries.

Should you have any further questions, please feel free to contact the Microsoft Fabric Community.

Thank you.

v-pnaroju-msft
Community Support
Community Support

Thank you, @burakkaragoz and @Akash_Varuna for your response.

Hi nirupamroy,

We would like to check if the solution provided by @burakkaragoz , @Akash_Varuna has resolved your issue. If you have found an alternative approach, we encourage you to share it with the community to assist others facing similar challenges.
If you found the response helpful, please mark it as the accepted solution and add kudos. This recognition benefits other members seeking solutions to similar queries.

Thank you.

Yes, the issue finally got resolved. After extensive brainstorming and multiple back-and-forth conversations with the local IT team at the office, we identified that the root cause was Zscaler, a cloud-based security platform that had been installed a few weeks ago. Its SSL inspection feature was interfering with the connection between Azure Databricks and Power BI. We resolved the issue by disabling SSL inspection for the API that pulls data from Azure Databricks (Azure Blob inspection bypass) and installing the Zscaler root CA certificates for Databricks Connect, which we also configured for Power BI.

Hi @nirupamroy,

Thank you for sharing your insights and approach in resolving the issue.

We kindly request you to mark your response as the accepted solution, as this will help other community members find answers to similar challenges more efficiently.
Please continue leveraging the Fabric Community for any further assistance with your queries.

Thank you.

Akash_Varuna
Community Champion
Community Champion

Hi @nirupamroy It is likely because of certificate validation or outdated Simba ODBC drivers. Ensure the certificate chain is valid and accessible, update the Simba Spark ODBC driver to the latest version, and verify no network blockages affect CRL access. Temporarily disable SSL revocation checks in the ODBC driver settings for testing. If issues persist, refresh cached metadata in Power BI and reconfigure the data connection.

burakkaragoz
Community Champion
Community Champion

Hi @nirupamroy ,


This error is related to SSL/TLS certificate validation when Power BI tries to refresh data from Azure Databricks. It usually means that Power BI cannot validate the certificate presented by Databricks—either due to missing or untrusted root certificates, network restrictions, or an incomplete certificate chain.

Here are some recommended steps to resolve this issue:

  1. Validate the Certificate Chain:
    Ensure that the SSL/TLS certificate used by your Databricks cluster is valid, not expired, and signed by a trusted authority. If the certificate was recently changed or updated, make sure all intermediates and root certificates are also valid.

  2. Update Root Certificates:
    On your Power BI machine, update the Windows root certificates. You can do this via Windows Update, or by downloading and installing the latest root CA certificates.

  3. Check Network Access for Certificate Validation:
    Certificate validation requires the ability to reach certificate revocation lists (CRL) or OCSP endpoints. Make sure your network, proxy, or firewall does not block access to these URLs. If your organization restricts outbound traffic, you may need to allowlist URLs related to the certificate authority.

  4. Update the ODBC Driver:
    Ensure you are using the latest Microsoft Spark ODBC driver for Power BI. Newer drivers often resolve certificate and connectivity issues.

  5. Restart Power BI and Your Machine:
    After performing these steps, restart both Power BI Desktop and your computer to ensure the new settings and certificates take effect.

If the issue persists after these steps, contact your IT team to review certificate trust settings or open a ticket with Microsoft Support for further assistance.

Let me know if you need detailed instructions on any of the steps above!

Helpful resources

Announcements
June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.