Error configuring Azure Databricks datasource using an On-Prem Data Gateway

[EdouardLC]

Hello,

We are currently configuring a Datasource to connect Power BI to an Azure Databricks SQL Warehouse throught a Power BI Data Gateway installed on a Azure VM.

• The gateway is well installed in our VM without any issue ;
• The gateway is Online in Power BI Service ;
• We managed to connect to our Azure Databricks workspace and run queries using the VM ;
• No Network issue found ; 
• For a test purpose, we manage to use this gateway to connect to a Sharepoint source ;
• We faced the same issue using PAT and OAuth authentification.
• We faced the same issue using September and October Data Gateway Version ;
• We already try to uninstall the Power BI Data Gateway.

The error message is the following : ODBC: ERROR [IM003] Specified driver could not be loaded due to system error 126: The specified module could not be found. (Simba Spark ODBC Driver New, C:\Program Files\On-premises data gateway\m\ODBC Drivers\New\Spark\SparkODBC_sb64.dll).

This DLL file is available in our VM at the same PATH :

Any idea ?

Thank you very much,
Best regards,
Edouard

[EdouardLC · Accepted solution]

Answer from Microsoft :

Cause \ Resolution

This error is because you are not able to access a CRL (certificate revocation list ) URL. The customer will need to find out why they are not able to access the CRL URL. This URL was added to the new driver as a security feature update. Most likely, the customer will need to include it in their allow list.
This behavior will not be reverted in future releases of the GW, hence the justification for the GW versions behavior and the solution moving forwards is what is mentioned in the statement above.

The CRL URL you need to allow is  http://*.digicert.com/*

This change will be permanent, that means all the Gateway versions will have this setting set to False:
<setting name="MashupFlightUseOldSparkDriver" serializeAs="String">

             <value>False</value>

</setting>

If you don’t to allow that CRL URL, the workaround is to change that setting to True, on the C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file

[Anonymous]

Same issue for me !