[BigQuery] (310) Storage API Error: Error: { code: UNKNOWN, message: Stream removed }

[songogeta32]

I am getting this error for big projects which have large number of rows - 

Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: [DataSource.Error] ERROR [HY000] [Microsoft][BigQuery] (310) Storage API Error: Error: { code: UNKNOWN, message: Stream removed }. '.

And I am not using ODBC driver but Google Big Query connector to connect to GCP Big Query. Though I have ODBC Simba driver installed in my VM. What is the issue here?

I noticed one thing this error we are only facing in a shared vm(among 9 members). When I am working on a personal Azure vm then this error is not coming and data is also loading very fast. Both have same ram(32 GB) and cpu(xeon 8272cl vs 8370c) and are in same network zone. What can be issue here?

[Anonymous]

Hi, @songogeta32 

Thanks @AmiraBedh . You can try the following method, which is from another case:

Re: OLE DB or ODBC error: [DataSource.Error] ERROR... - Microsoft Fabric Community

You can also try clearing your cache, as you will be guided in the following article.

How to solve OLE DB or ODBC errors in PowerBI - CloudFronts

How to Get Your Question Answered Quickly

If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .

Best Regards

Jianpeng Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[songogeta32]

@Anonymous   I had a discussion with Google Team. They know about the issue, they mentioned that on retry this can be solved easily. But it seems like the Google BQ connector doesnt have the retry mechanism. Is this being worked upon?

[Anonymous]

Hi, @songogeta32 

Thank you very much for your reply. While there is no direct reconnect button, you can try to re-establish the connection or add credentials, you can try it.

In addition, you can try to adjust the timeout period to see if it will be reconnected within the specified time, the documentation for the advanced settings is as follows:

Google BigQuery (Microsoft Entra ID) (Beta) - Power Query | Microsoft Learn

You can also try the two methods of the previous reply.

Best Regards

Jianpeng Li

[songogeta32]

https://issuetracker.google.com/issues/240305081?pli=1

Google confirmed its an open issue from their side. But the error can be handled from client side also i.e. if Google BigQuery connector implements retries in RPC API calls then this will be solved.

[Anonymous]

A possible solution may be adjusting the default connector parameter's formatting that the UI populates into the M script.

Change from:

• Source = GoogleBigQuery.Database([UseStorageApi = true, ConnectionTimeout = null, CommandTimeout = null, BillingProject = "some-project-name", ProjectId = "some-project-name"]),
  #"Navigation 1" = Source{[Name = "some-project-name"]}[Data]

Change to:

• Source = GoogleBigQuery.Database([UseStorageApi = true, BillingProject = "some-project-name", ConnectionTimeout = #duration(0, 0, 5, 0), CommandTimeout = #duration(0, 2, 0, 0)]),
  #"Navigation 1" = Source{[Name = "some-project-name"]}[Data]

It's worth a try as it seems to have fixed the problem for me, and I don't believe anything else was modified...good luck!

[songogeta32]

Also we are using Google Big Query connector then why the error is related to ODBC. We have installed odbc driver but we are not using!

[songogeta32]

No the retry logic should be inside the Google BQ connector, not for user to something to worry about. The API call inside the BQ connector should be retried.

[AmiraBedh]

You may need to post it in the issues section
https://community.powerbi.com/t5/Issues/idb-p/Issues


If you have Pro subscription, open a support ticket.Go to https://support.powerbi.com > Scroll down > "CREATE SUPPORT TICKET".