Forum Discussion
The error Could not load file or assemblyPower BI Refresh Error on BigQuery Tables - Missing ADBC As
Thank you for the suggestions.
Refreshing a single affected table still fails with the same ADBC error. The issue does not appear to be related to table size . The only consistent difference is that the failing queries use the BigQuery connector with Implementation="2.0". Switching them back to the default implementation resolves the problem.
- v-ssriganesh7 months agoCommunity Support
Hello gauravpatil-liv,
We appreciate your efforts and are pleased to hear that your issue was resolved. This will assist other community members in resolving similar issues more efficiently.- mattAtBradyCorp7 months agoFrequent Visitor
This isn't a resolution. Telling people to use an older version is a workaround.
- v-ssriganesh7 months agoCommunity Support
Hello mattAtBradyCorp,
Thanks for your reply. you’re correct.To clarify, this isn’t a permanent fix but a workaround. The behavior appears to be tied to the newer Implementation = "2.0" path in the current Power BI Desktop build. Switching back to Implementation = "1.0" allows users to continue working until this is addressed in a future update.
If this issue is a priority in your environment or continues to impact your workflows, we recommend raising a Microsoft support ticket so it can be investigated further.
You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketBest regards,
Ganesh Singamshetty.
- araoim7 months agoFrequent Visitor
I have the same problem when I'm trying to refresh reports that are using a Databricks connection or when I'm trying to connect to a new table using Dtabricks connection. Because I've already have the query generated for the existing reports I was able to change the Implementation=2.0 to Implementation=1.0 and is working like this
Databricks.Catalogs(
ServerDataBricks,
PathDataBricks,
[
Catalog = CatalogDataBricks,
Database = null,
QueryTags = null,
EnableAutomaticProxyDiscovery = null,
Implementation = "1.0",
EnableQueryResultDownload="0"
]- v-ssriganesh7 months agoCommunity Support
Hello araoim,
Please consider raising a Microsoft support ticket for further investigation. You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket - senorbol7 months agoFrequent Visitor
Hi Everyone,
I had the same issue on the Jan 2026 release of Power BI Desktop. It looks like the implementation option in the Databricks connection GUI has set itself to 2.0 (beta) automatically.
Change this to default in the options and this resolved the issue for me.