Troubleshooting BigQuery Data Transfer Service Transfer Setup

Overview

This document is intended to help you troubleshoot the most common issues encountered when setting up a transfer. This document does not encompass all possible error messages or issues, nor does it focus on errors experienced after creating a transfer.

If you are experiencing issues that are not covered in this document, contact BigQuery Data Transfer Service support.

Examining errors in the run history

If your initial transfer run fails, examine the details in the run history:

  1. Open the transfers page in the BigQuery web UI.

    Go to the BigQuery web UI

    As your scheduled transfers are run, the BigQuery web UI updates the transfer status. Successful transfers are marked with a check mark inside a green circle. Failed transfers are marked with an exclamation point inside a red circle. Successful transfers with warnings (indicated by an exclamation point inside a yellow triangle) are not considered problematic unless the resulting tables appear abnormal.

  2. Click your failed transfer to open the transfer properties.

  3. The transfer properties page displays the Run History. Click the most recent failed run to view the log messages including any relevant error messages.

    Run history

General issues

When diagnosing general transfer issues, verify the following:

  • Verify that you have completed all the steps in the "Before You Begin" section of the documentation page for your transfer type.
  • The transfer configuration properties are correct.
  • The user account used to create the transfer has access to the underlying resources.

If your transfer configuration is correct, and the appropriate permissions are granted, refer to the following for solutions to commonly encountered issues.

Error: An unexpected issue was encountered. If this issue persists, please contact customer support.

Resolution: This error typically indicates a temporary outage or an issue within BigQuery. Wait approximately 2 hours for the issue to be resolved. If the problem persists, contact BigQuery Data Transfer Service support.

Error: Quota Exceeded.

Resolution: Transfers are subject to BigQuery quotas on load jobs. If you need to increase your quota, contact your Cloud Sales representative. For more information, see Calculating transfer quota usage.

DoubleClick Campaign Manager transfer issues

The following are common errors encountered when creating a DoubleClick Campaign Manager transfer.

Error: Import failed - no data was available for import. Please verify that data existence was expected or Error: No data available for the requested date. Please try an earlier run date or verify that data existence was expected.

Resolution: Verify you are using the correct ID for the transfer. If you are using the correct ID, verify the DoubleClick Campaign Manager Cloud Storage bucket contains Data Transfer V2.0 files for the specified date range. If the files exist, schedule a backfill for the affected date range. For more information on creating a DoubleClick Campaign Manager backfill request, see Set up a backfill.

Error: ACCESS_DENIED: gaia user [USER] does not have BUCKETS_GET access to bucket [BUCKET].

Resolution: The user creating the DoubleClick Campaign Manager transfer must have read access to the Cloud Storage bucket containing the Data Transfer V2.0 files. You can obtain information about the Cloud Storage bucket and request access from your DoubleClick administrator.

DoubleClick for Publishers transfer issues

The following are common errors encountered when creating a DoubleClick for Publishers transfer.

Error: No data available for the requested date. Please try an earlier run date or verify that data existence was expected.
Error: Import failed - no data was available for import. Please verify that data existence was expected.

Resolution: Verify the DoubleClick for Publishers Cloud Storage bucket contains data transfer files for the specified date range. Your DoubleClick administrator manages the Cloud Storage bucket containing your Data Transfer files. Users creating DoubleClick transfers must be members of the Google Group with read access to the bucket.

You can verify Cloud Storage permissions by attempting to read files in the DoubleClick Data Transfer bucket. For more information on DoubleClick for Publishers Cloud Storage buckets, see Access DFP storage buckets.

If the files exist in the Data Transfer bucket and you have read permissions, schedule a backfill for the affected date range. For more information on creating a DoubleClick for Publishers backfill request, see Set up a backfill.
Error: AuthenticationError: NO_NETWORKS_TO_ACCESS.

Resolution: Ensure you have read access to the DoubleClick for Publishers network. If you need assistance determining network access, contact DoubleClick for Publishers support.

Error: Error code 9 : Field [FIELD_NAME]?[FIELD_NAME]?[FIELD_NAME]?RefererURL is unknown.; Table: [TABLE_NAME]

Resolution: Ensure you are not using the thorn (þ) delimiter. The thorn delimiter is currently unsupported. Use of the thorn is indicated by the ? in the error message.

Google AdWords transfer issues

The following are common errors encountered when creating a Google AdWords transfer.

Error: CUSTOMER_SERVING_TYPE_REPORT_MISMATCH.

Resolution: AdWords manager accounts (MCCs) are not currently supported. Until the BigQuery Data Transfer Service adds support for AdWords manager accounts, you must create a separate transfer for each customer ID.

Error: Import failed - no data was available for import. Please verify that data existence was expected or Error: No data available for the requested date. Please try an earlier run date or verify that data existence was expected.

Resolution: If you receive this error when you are creating a Google AdWords transfer, contact BigQuery Data Transfer Service support and include a screen capture of the error message.

Error: AuthenticationError.NOT_ADS_USER.

Resolution: The user setting up the Google Adwords transfer must have a Google AdWords account/login.

YouTube transfer issues

The following are common errors encountered when creating a YouTube transfer.

Error: Import failed - no data was available for import. Please verify that data existence was expectedor Error:No data available for requested date. Please try an earlier run date or verify that data existence was expected.

Resolution: If you have not previously created YouTube reporting jobs, allow YouTube at least 2 days for the BigQuery Data Transfer Service to generate the reports on your behalf. No additional action is required. Transfers will fail for the first 2 days and should succeed on day 3. If you have previously created YouTube reporting jobs, confirm the user creating the transfers has read access to the reports.

Error: No reports for reporting job with name [NAME].

Resolution: This is not an error. It is a warning that indicates no data was found for the specified report. You can ignore this warning. Future transfers will continue to run.

YouTube permissions issues

For YouTube Content Manager reports, the user setting up the transfer must have CMS user permissions (at a minimum). CMS user permissions must be granted to each content manager for whom you are creating a transfer.

Calculating transfer quota usage

Transfers are subject to BigQuery quotas on load jobs. It’s important to consider how many transfers you enable in each project to prevent transfers and other custom data loads from producing “quota exceeded” errors.

You can use the following equation to estimate how many load jobs are required by your transfers:

Number of jobs = Number of transfers x Number of tables x Refresh window

Where:

  • Number of transfers is the number of transfer configurations you enable in your project.
  • Number of tables is the number of tables created by each specific transfer type. The number of tables varies by transfer type:

    • Google AdWords transfers create 61 tables.
    • DoubleClick for Publishers transfers create 36 tables.
    • DoubleClick Campaign Manager transfers create 25 tables.
    • YouTube transfers create 52 tables.
  • Refresh window describes how often the transfer runs. Transfer run schedules are provided for each transfer type:

Monitor your resources on the go

Get the Google Cloud Console app to help you manage your projects.

Send feedback about...