Databricks Connector Error: SSL Certificate Revocation status unknown during result download

[traderbi]

Hi everyone,

Has anyone recently encountered an SSL revocation error when pulling data via the Databricks connector?

Environment:

• Tool: Power BI Service

• Connector: Databricks (Import)

The Error: The connection succeeds, but large query execution fails when downloading result files from cloud storage with this error:

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 9b4bea0c-f931-4b2b-a16d-d93f1777df05: 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 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 "D:\MWC\WorkloadPackages\AS\2026.7.1.21\valid\MDataEngine\ODBC Drivers\Spark\en-US\DSMessages.xml" or "D:\MWC\WorkloadPackages\AS\2026.7.1.21\valid\MDataEngine\ODBC Drivers\Spark\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.'.. </ccon>. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.

[traderbi · Accepted solution]

Thanks @powerbidev123 . The issue only started a couple of days ago and has affected multiple workbooks which seems too coincidental. I suspect something has changed which has triggered the problem and am now testing  EnableQueryResultDownload="0" to bypass the problem.

[traderbi]

Adding EnableQueryResultDownload="0" resolved the issue.

[powerbidev123]

Hi @traderbi 

Most common causes

• Blocked CRL/OCSP access from the runtime handling the download
• Proxy or firewall inspection breaking certificate validation
• Outdated Databricks / Spark / ODBC components
• Private endpoint / VNet / storage firewall restrictions
• Less commonly: a certificate chain issue on the storage endpoint itself

What you can check

1. Test whether only large result sets fail
   If small extracts work and large ones fail, that strongly confirms the cloud-fetch path.

2. Review storage/network access

   • If Azure storage is involved, check outbound access and certificate validation paths.
   • If there’s a proxy or firewall, make sure CRL/OCSP endpoints are reachable.

3. Update Databricks connector/runtime

   • Use the latest supported Databricks connector/runtime on both sides if possible.

4. Reduce query size as a workaround

   • Filter earlier
   • Materialize source tables/views
   • Split the import into smaller partitions or tables