Google BigQuery updated linked service error: "Message=No current element is available" for empty result

Hello Quyen Dang,

Welcome to the Microsoft Q&A forum.

This is a known issue, and a product backlog item has been submitted to address it.

Unfortunately, I don't have an ETA. However, I can update this thread once I hear back from the product team.

Thanks for reporting this, was there any update on it on this one, please @Bhargava-MSFT

Yes, same error message when empty table or zero records returned from the query.

So, in the copy activity of my pipeline
Input as below

{
 "source": {
        "type": "GoogleBigQueryV2Source",
        "query": "SELECT * FROM ****Dataset******.*************table**************"
    },
    "sink": {
        "type": "DelimitedTextSink",
        "storeSettings": {
            "type": "AzureBlobStorageWriteSettings"
        },
        "formatSettings": {
            "type": "DelimitedTextWriteSettings",
            "quoteAllText": true,
            "fileExtension": ".txt"
        }
    },
    "enableStaging": false,
    "translator": {
        "type": "TabularTranslator",
        "typeConversion": true,
        "typeConversionSettings": {
            "allowDataTruncation": true,
            "treatBooleanAsNumber": false
        }
    }
}

I get error message

ErrorCode=UserErrorFailedFileOperation,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The file operation is failed, upload file failed at path: '#####ADLSPATH########'.,Source=Microsoft.DataTransfer.Common,''Type=Microsoft.DI.Connector.GoogleBigQuery.ExceptionUtils.GoogleBigQueryConnectorException,Message=Error occurred when reading, ErrorCode: UnknownError,Source=Microsoft.DI.Connector.GoogleBigQuery,''Type=System.InvalidOperationException,Message=No current element is available.,Source=Grpc.Core,'

Appreciate your assistance

Monem Metwally

Thank you for the confirmation. I will check with my team and get back to you.

Hello Monem Metwally

<Update>

If you are using SHIR, you need to upgrade to the next version and try again.