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

Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now

Unable to connect to Databricks from Power BI Desktop (ODBC error)

Since today we can't connect to our Azure Databricks instances through PBI Desktop. It seems like there is an issue with the ODBC driver.

 

Error message: "DataSource.MissingClientLibrary: The 'Driver' property with the value '{Simba Spark ODBC Driver}' does not match an installed ODBC driver."

 

Is this a Power BI issue? Maybe an issue in the latest PBI update? PBI Desktop version 2.132.1053.0

Status: Delivered

Hi all , 

Thank you @AlexGorev  for your reply. I will change the status to "Delivered" . This allows other customers with the same problem to see the solution.

 

Best Regards,
Community Support Team _ Ailsa Tao

Comments
jackmulligancs
New Member

Same issue also happening for us on Snowflake

Herm1995
Regular Visitor

Same issue for me since today.

maxbarj
Regular Visitor

Same issue here

lamysroe
Advocate I

Same

Herm1995
Regular Visitor

Raised an support ticket, lets see what will happen.

BjornBerg
Regular Visitor

Same issue here. I thought it was related to the Databricks ODBC driver that I installed to connect Excel with Databricks. But after removing both this driver and Power BI desktop and installing desktop again, the problem is still there.

baaag
Regular Visitor

Same since today.

nawhiteley
Regular Visitor

Having the exact same problem. I am still on the August version though (Version: 2.132.1053.0 64-bit (August 2024)).

Dataflows are completing fine in the service and this exact same desktop file was executing the exact same queries just fine yesterday. It doesn't feel like a Databricks issue to me.

I tried grabbing a new connection file for Power BI from Databricks and it has the same issue

mjkusler
Regular Visitor

Same issue....Nothing has worked, but I'm now getting a new error instead of the ODBC driver error.

 

mjkusler_0-1726675847846.png

 

mjkusler
Regular Visitor

I tried rolling back to the July desktop version. No luck.