Failed Getting All Data Needed for Transfer Please Try Again

This document is intended to help you troubleshoot the near common issues encountered when setting upward a transfer. This document does not encompass all possible fault messages or bug.

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

Before contacting Cloud Client Care, capture transfer configuration and transfer run details. For information on how to get these details, run across Getting information almost transfers and Viewing transfer run details and log messages.

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 assist y'all identify an appropriate resolution using this document.

Before contacting Customer Care, capture whatever relevant data from the run history including any error letters.

General issues

When diagnosing general transfer issues, verify the following:

• Verify that yous have completed all the steps in the "Earlier You Brainstorm" department of the documentation page for your transfer type.
• The transfer configuration properties are correct.
• The user business relationship used to create the transfer has admission to the underlying resource.

If your transfer configuration is right, and the appropriate permissions are granted, refer to the following for solutions to unremarkably encountered problems.

Fault: An unexpected issue was encountered. If this issue persists, please contact client back up.

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

Error: Quota Exceeded.

Resolution: Transfers are bailiwick to BigQuery quotas on load jobs. If yous demand to increase your quota, contact your Cloud Sales representative. For more data, see Quotas and limits.

Fault: The caller does non take permission.

Resolution: Confirm the signed-in business relationship in Google Cloud console is the aforementioned every bit the business relationship you lot select for BigQuery Data Transfer Service when creating the transfer.

• Signed-in account in Google Cloud panel:

  

• Choose an account to continue to BigQuery Data Transfer Service:

  

Campaign Manager transfer issues

The following are mutual errors encountered when creating a Campaign Managing director transfer.

Fault: Import failed - no data was bachelor for import. Please verify that data existence was expected.

Error: No data available for the requested engagement. Delight attempt an earlier run date or verify that information existence was expected.

Resolution: Verify you lot are using the correct ID for the transfer. If yous are using the right 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 afflicted appointment range. For more information on creating a Entrada Manager backfill asking, see setting up a backfill.

Y'all tin can verify whether the files existed when the transfer run was scheduled by checking the created fourth dimension of the files in the Cloud Storage bucket. In some cases, the starting time transfer run of the day may exist scheduled prior to the generation of the first batch of Campaign Manager Data Transfer files. Subsequent runs on the same mean solar day and the following day will load all the files generated by Campaign Manager.

Error: A permission denied error was encountered: PERMISSION_DENIED. Please ensure that the user account setting upwardly the transfer config has the necessary permissions, and that the configuration settings are correct.

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

Google Ads transfer bug

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

Fault: Import failed - no data was available for import. Delight verify that data beingness was expected.

Fault: No data available for the requested date. Please try an before run date or verify that data beingness was expected.

Resolution: If you lot 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 upward the Google Ads transfer must accept a Google Ads account/login.

Mistake: 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 selection in the transfer configuration and ready a backfill to attempt to recall data for the days impacted by the failed transfer run.

Warning: Data for the written report ClickStats was not available for the specified engagement.

Error: INVALID_DATE_RANGE_FOR_REPORT.

Resolution: This is expected when backfilling Click Performance Study information for more than 90 days back. In this case, y'all volition encounter the above alarm/error and the ClickStats table will not exist updated for the specified appointment.

Google Ad Manager transfer issues

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

Error: No information bachelor for the requested date. Please endeavour an earlier run date or verify that data existence was expected.

Fault: Import failed - no data was available for import. Please verify that data beingness was expected.

Resolution: Verify the Google Ad Manager Deject Storage bucket contains information transfer files for the specified date range. Your Google Ad Manager administrator manages the Cloud Storage saucepan containing your Data Transfer files. Users creating Google Ad Manager transfers must exist members of the Google Group with read access to the bucket.

Y'all can verify Cloud Storage permissions by attempting to read files in the Google Advertisement Manager Data Transfer bucket. For more than data on Google Ad Managing director Cloud Storage buckets, see Access Google Advertising Managing director storage buckets.

You tin verify whether the files existed when the transfer run was scheduled past checking the created time of the files in the Cloud Storage bucket. In some cases, the kickoff transfer run of the day may be scheduled prior to the generation of the outset batch of Google Advertizement Managing director Data Transfer files. Subsequent runs on the same day and the post-obit day will load all the files generated past Google Ad Managing director.

If the files be in the Data Transfer bucket and you take read permissions, schedule a backfill for the affected date range. For more information on creating a Google Ad Manager backfill request, run across Set upwards a backfill.

Error: AuthenticationError: NO_NETWORKS_TO_ACCESS.

Resolution: Ensure y'all accept read access to the Google Ad Manager network. If you lot need assistance determining network admission, contact Google Advertizement Manager back up.

Fault: Error lawmaking 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. Employ of the thorn is indicated by the ? in the error message.

Google Merchant Center transfer issues

The post-obit are common errors encountered when creating a Google Merchant Center transfer.

Mistake: No information to transfer found for the Merchant account. If yous have just created this transfer - you may demand to wait for upward to 90 minutes before the data of your Merchant account are prepared and available for the transfer.

Resolution: Y'all receive this mistake if you fix a transfer using the default starting date and time in the Schedule section. If you use the default scheduling values, the get-go transfer run starts immediately afterwards the transfer is created, only it fails because your Merchant account data must exist prepared before it can be transferred. Wait 90 minutes and and so prepare a backfill for today, or you tin can look until tomorrow for the next scheduled run.

Error: No data to transfer found for Merchant account. This tin can be considering your business relationship currently doesn't take any products.

Resolution: This error indicates that your Merchant account has no products. The transfer will brainstorm working once you add products to your Merchant account.

Error: Transfer user doesn't have admission to the Merchant account. Please verify access in the Users department of the Google Merchant Center.

Resolution: This error indicates that the user who prepare 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: Transfer user doesn't have user roles that allows access to the product information of the Merchant account. Please verify access and roles in the Users section of the Google Merchant Center.

Resolution: This fault indicates that the user who gear up upwards the transfer doesn't accept access to the product data of the Merchant account used by the transfer. To resolve the outcome, verify and grant missing user roles in the Google Merchant Heart.

Error: Historical backfills are currently non supported.

Resolution: You receive this error if you lot set upwards a backfill for previous days. This error is expected. Historical backfills are not currently supported. You can just fix a backfill for today to refresh today's data after the scheduled daily run has already finished.

YouTube transfer bug

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

Error: Import failed - no information was bachelor for import. Please verify that data existence was expected.

Error: No information available for requested date. Please try an earlier run appointment or verify that data existence was expected.

Resolution: If y'all have not previously created YouTube reporting jobs, permit YouTube at least 2 days for the BigQuery Information Transfer Service to generate the reports on your behalf. No additional action is required. Transfers volition neglect for the beginning 2 days and should succeed on mean solar day 3. If you have previously created YouTube reporting jobs, confirm the user creating the transfers has read admission to the reports.

Also, verify the transfer was gear up for the correct account. In the OAuth dialog, you must select the channel for which you would like to load information.

Error: No reports for reporting task with proper noun name.

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

Effect: The resulting tables created by the transfer are incomplete, or the results are unexpected.

Resolution: If you accept multiple accounts, you lot must choose the correct account when you receive the YouTube permissions dialog.

Issue: Data doesn't match betwixt YouTube Analytics and BigQuery YouTube Transfers.

Background: BigQuery YouTube transfers use YouTube reporting API to ingest data directly into a BigQuery dataset. On the other hand, Youtube Analytics Dashboard pulls information using YouTube Analytics API. The numbers that YouTube produces in their generated Reporting API should be treated as the final numbers, whereas the numbers visible in the YouTube Analytics Dashboard/API should be treated as estimated numbers. Some degree of discrepancy between the two APIs is expected.

Resolution: If the reported numbers are indeed incorrect, so both YouTube's system and BigQuery Data Transfer Service YouTube transfer are set up to backfill missing numbers and make them available in new generated reports for the backfilled days. Because a BigQuery Information Transfer Service YouTube configuration just loads all available reports created by YouTube Reporting API, when BigQuery transfer automatically imports future generated YouTube Reports, information technology will also account for the newly generated and updated data, and ingest information technology into the correct Appointment division table.

YouTube permissions issues

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

Quota bug

Error: Quota exceeded: Your projection exceeded quota for imports per projection.

Resolution: Verify you take not scheduled too many transfers in your project. For information on calculating the number of load jobs initiated by a transfer, run across Quotas and limits.

caroanxionce.blogspot.com

Source: https://cloud.google.com/bigquery-transfer/docs/transfer-troubleshooting

Share this post