ADBC: Could not load file or assembly Apache.Arrow.Adbc.Telemetry.Traces.Listeners

[Prajjval]

I am getting this error after the recent update it is not getting to BigQuery was working efficient for past 4 months now its showing this error. Any solution

[v-pgoloju]

Hi @Prajjval,

Just checking, have you had a chance to open a support ticket, as suggested. If so, we'd love to hear the current status or any updates from that.

If the issue was resolved through the support ticket, it would be great if you could share the solution here as well. It could really help other community members find answers more quickly.

Warm regards,
Prasanna Kumar

[v-pgoloju]

Hi @Prajjval,

If the issue still persists, I’d recommend raising a support ticket with Microsoft. The support team can look into the backend and provide more in-depth assistance tailored to your environment.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

Thanks & Regards,

Prasanna Kumar

[charleshale]

Isnt this is a bug with the Jan release?

[nidhippatel]

In power query, I just replaced "=GoogleBigQuery.Database([Implementation="2.0"])" with "=GoogleBigQuery.Database()" and it worked for me.

[oliblabla]

I had the same error for loading Azure Databricks and changing in Implementation(optional) from 2.0 to default worked for me.

[LisaYYYYYY]

I had the same issue happen around the same time last Friday. As a solution, you should go to Settings -> Option and settings -> Options -> Preview features 

Make sure to UNSELECT "Use new Google BigQuery connector implementation" and restart Power BI. This should solve your issue!

[Prajjval]

its still showing the same error

[user1023]

I got the same problem and I did workaround by changing Implementation="2.0" to Implementation= null in Query Editor Tab but this only worked on old files created before. In the new one, I cannot connect to the bigquery and there's no way to open Query Editor to workaround like above 

[Tony-0123456]

I've had similar issues with new reports.  The Authentication fix offered by MohitsinghMS is probably the correct method but if it doesn't work for you, there are 2 workarounds that I've used:

1. Copy/paste a query from an older report into the new one, then edit as needed.
2. Go into Options->Preview Features, and uncheck the "Use new Google BigQuery connector implementation" option.  This may require a program restart.

[MohitsinghMS]

Sometimes the inability to connect in a new file is caused by Power BI trying to reuse an old, cached credential token that is stuck on "Implementation 2.0" settings.

1. In Power BI Desktop, go to File > Options and settings > Data source settings.

2. Look for Google BigQuery in the list (under "Global permissions").

3. Select it and click Clear Permissions.

4. Click Delete.

5. Try to connect via "Get Data" > "Google BigQuery" again. This will force a fresh authentication handshake.

[Tony-0123456]

I also started getting this error today with my Bigquery connections.  Removing the Implementation seems to fix it for me, but it seems to revert and re-add it every time I click the gear and edit my source query.

Change:

= Value.NativeQuery(GoogleBigQuery.Database([BillingProject="my-project", Implementation="2.0"]){[Name="

To:

= Value.NativeQuery(GoogleBigQuery.Database([BillingProject="my-project"]){[Name="

[dmarasaruffle]

I too began getting this same error for both Snowflake & BigQuery native connectors as of this morning.

[MohitsinghMS]

1. Clear Power BI Data Cache (Most Likely Fix)

Old cache files often conflict with new updates.

1. Open Power BI Desktop.

2. Go to File > Options and settings > Options.

3. Under Global, select Data Load.

4. Click Clear Cache under "Data Cache Management Options" and "Q&A Cache Options".

5. Restart Power BI and try connecting again.

2. Disable "Use Google BigQuery Storage API" (Workaround)

The error references Apache.Arrow, which is a library heavily used by the BigQuery Storage API for faster data transfer. Disabling this might bypass the broken connector file and let you work (though it might be slower).

1. In Power BI, go to Transform Data (Power Query Editor).

2. Right-click your BigQuery query/source and select Advanced Editor (or just double-click the Source step).

3. In the GoogleBigQuery.Database function, look for an option like UseStorageApi = true.

4. Change it to UseStorageApi = false or remove the parameter to default to the standard API.

• Note: If you are connecting via the main dialog, look for a checkbox that says "Use High-Speed Storage API" and uncheck it.

3. Clean Reinstall of Power BI Desktop

If the specific DLL file is actually missing from your computer, a simple reinstall usually fixes it.

1. Uninstall Power BI Desktop.

2. Restart your computer (Important: this clears locked DLL files).

3. Download and install the latest version again from the Microsoft Store or the official download site.

4. Check On-Premises Data Gateway (If applicable)

If this error is happening on the Power BI Service (online) rather than Desktop:

• Your On-Premises Data Gateway is likely outdated.

• The Gateway version must match the Desktop version (or be newer) to have the correct BigQuery drivers. Update your Gateway to the latest release.

[charleshale]

These changes for me are failing to address the issue.  And while remove Implemention-"2.0" nominally works for running scripts, that deletion changes how the query handles nested types (STRUCT/ARRAY) -- so it's a material issue.

It is a known bug https://support.fabric.microsoft.com/known-issues/?product=Power%2520BI&active=true&fixed=true&sort=...