Troubleshooting transfer configurations

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.

If you are experiencing issues that are not covered in this document, you can request support.

Examining errors in the run history

If your initial transfer run fails, examine the details in the run history. Errors listed in the run history can help you identify an appropriate resolution using this document.

Before contacting Google Cloud Support, capture any relevant information from the run history including any error messages.

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 you intend to create transfers using the classic BigQuery web UI, allow pop-ups from bigquery.cloud.google.com so you can view the permissions window. You must allow the BigQuery Data Transfer Service permission to manage your data for the transfer to succeed.

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, request 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.

Campaign Manager transfer issues

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

Error: Import failed - no data was available for import. Please verify that data existence was expected.
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 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 Campaign Manager backfill request, see Set up a backfill.
Error: A permission denied error was encountered: PERMISSION_DENIED. Please ensure that the user account setting up the transfer config has the necessary permissions, and that the configuration settings are correct.
Resolution: The user creating the 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 Google Ad Manager administrator.

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

Error: Import failed - no data was available for import. Please verify that data existence was expected.
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 Ads transfer, request support and include a screen capture of the error message.
Error: AuthenticationError.NOT_ADS_USER.
Resolution: The user setting up the Google Ads transfer must have a Google Ads account/login.
Error: ERROR_GETTING_RESPONSE_FROM_BACKEND.
Resolution: If a Google Ads transfer run fails and returns ERROR_GETTING_RESPONSE_FROM_BACKEND, enable the Exclude Removed/Disabled Items option in the transfer configuration and set up a backfill to attempt to retrieve data for the days impacted by the failed transfer run.

The following are common errors encountered when creating a Google Ad Manager 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 Google Ad Manager Cloud Storage bucket contains data transfer files for the specified date range. Your Google Ad Manager administrator manages the Cloud Storage bucket containing your Data Transfer files. Users creating Google Ad Manager 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 Google Ad Manager Data Transfer bucket. For more information on Google Ad Manager Cloud Storage buckets, see Access Google Ad Manager 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 Google Ad Manager backfill request, see Set up a backfill.

Error: AuthenticationError: NO_NETWORKS_TO_ACCESS.

Resolution: Ensure you have read access to the Google Ad Manager network. If you need assistance determining network access, contact Google Ad Manager 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 Merchant Center transfer issues

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

Error: No data to transfer found for the Merchant account. If you have just created this transfer - you may need to wait for up to 90 minutes before the data of your Merchant account are prepared and available for the transfer.
Resolution: You receive this error if you set up a transfer using the default starting date and time in the Schedule section. If you use the default scheduling values, the first transfer run starts immediately after the transfer is created, but it fails because your Merchant account data must be prepared before it can be transferred. Wait 90 minutes and then set up a backfill for today, or you can wait until tomorrow for the next scheduled run.
Error: No data to transfer found for Merchant account. This can be because your account currently doesn't have any products.
Resolution: This error indicates that your Merchant account has no products. The transfer will begin working once you add products to your Merchant account.
Error: Transfer user doesn't have access to the Merchant account. Please verify access in the Users section of the Google Merchant Center.
Resolution: This error indicates that the user who set up the transfer doesn't have access to the Merchant account used by the transfer. To resolve the issue, verify and grant missing account access in the Google Merchant Center.
Error: Historical backfills are currently not supported.
Resolution: You receive this error if you set up a backfill for previous days. This error is expected. Historical backfills are not currently supported. You can only set up a backfill for today to refresh today's data after the scheduled daily run has already finished.

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 expected.
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.

Also, verify the transfer was set up for the correct account. Specifying the correct YouTube page ID is not sufficient. In the OAuth dialog, you must select the channel for which you would like to load data.

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.

Issue: The resulting tables created by the transfer are incomplete, or the results are unexpected.
Resolution: If you have multiple accounts, you must choose the correct account when you receive the YouTube permissions dialog. Specifying the correct YouTube page ID without choosing the correct account will give you unexpected results.

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.

Quota issues

Error: Quota exceeded: Your project exceeded quota for imports per project.
Resolution: Verify you have not scheduled too many transfers in your project. For information on calculating the number of load jobs initiated by a transfer, see Transfer quotas.
Σας βοήθησε αυτή η σελίδα; Πείτε μας τη γνώμη σας:

Αποστολή σχολίων σχετικά με…

Αυτή η σελίδα
Χρειάζεστε βοήθεια; Επισκεφτείτε τη σελίδα υποστήριξής μας.