Source=Microsoft.WindowsAzure.Storage,StorageExtendedMessage=0:The property name is invalid.

Sidnei Dos Santos Barbosa 0 Reputation points
2023-08-24T06:37:54.49+00:00

Hey guys, can you help

I'm trying to run a very simple pipeline for a school assignment... When I create the copy task to a Table Storage, i have the message below:

Operation on target ToTable failed: ErrorCode=FailedStorageOperation,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=A storage operation failed with the following error 'Element 0 in the batch returned an unexpected response code.'.,Source=,''Type=Microsoft.WindowsAzure.Storage.StorageException,Message=Element 0 in the batch returned an unexpected response code.,Source=Microsoft.WindowsAzure.Storage,StorageExtendedMessage=0:The property name is invalid.

Can you help?

Thanks in advance

Azure Table Storage
Azure Table Storage
An Azure service that stores structured NoSQL data in the cloud.
170 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,843 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,681 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sumarigo-MSFT 46,126 Reputation points Microsoft Employee
    2023-08-28T08:55:14.8033333+00:00

    @Sidnei Dos Santos Barbosa Firstly, Apologies for the dela response!

    For better understanding the issue: Can you please elaborate bit more on your query?
    Can you share the requestID ?

    Based on the error message, there is a similar discussion in the SO forum, please refer to the suggestion.
    It looks like you are encountering an error with a storage operation. The error message indicates that "Element 0 in the batch returned an unexpected response code" and that "the property name is invalid".

    This error can occur if there is an issue with the property name that you are trying to use. It is possible that the property name is misspelled or does not exist.

    To resolve this issue, you should check the property name that you are using and ensure that it is correct. You may also want to check the documentation for the storage service that you are using to ensure that you are using the correct property name and format.

    • If the issue persists, you may want to try running the storage operation again or contacting the support team for the storage service that you are using for further assistance.
      It sounds like you are being throttled by Table Storage. 200 Data integration units sound like enough parallelism to cause this, assuming each unit moves 100 entities per second, or all of them move 10 entities per second into the same partition. See table storage performance limits here.
    • Maximum request rate per storage account 20,000 transactions per second, which assumes a 1-KiB entity size
    • Target throughput for a single table partition (1 KiB-entities) Up to 2,000 entities per second

    In your case, I think reducing the Data integration units might actually be the solution. If you still need more throughput, options include using more storage accounts, bigger storage accounts, or changing architecture.

    Please let us know if you have any further queries. I’m happy to assist you further.


    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.