There are around 300 jobs that run each day and we may this issue may be 2 times a day or do not face this issue for 3-4 days at all.
Can anyone help me understand what is the cause of this issue and how do I resolve this ?
@Shubhadip Barman
May I know what kind files( ex: images, doc,, pdf or tar.gz) are you transferring?
Unluckily, I cannot reproduce it in my environment. Can you set a lower data transfer and try to see if it avoid the network errors? If the issue persist in the lower data transfer also, let me know the status and also share the screen shot of the error message
I assume this could happen due to connection reset, usually means network broken.
Workaround: You can try
Azcopy
Hope this helps!
Kindly let us know if the above helps or you need further assistance on this issue.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please don’t forget to
"Accept the answer”
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
I have attached the screenshot of the error.
We are uploading the .tsv files.
The file size is really not a matter because files with 1.3GB gets transferred easily. The HTTP Client error happens for any random size file, it may contain only 30 records or 400,000 records.
I am not sure when we connect BODS to Azure, is there a gateway URL that we mention or does it happen based on the Portal configuration where we say Azure BLOB ?
@Shubhadip Barman
We would like to work closer on this issue, This may require a deeper investigation, so If you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support. In this case, could you send an email to AzCommunity[at]Microsoft[dot]com referencing this thread. Please mention "ATTN subm" in the subject field and subscription ID. Thank you for your cooperation on this matter and look forward to your reply.
We have same error , loading with SAP BODS Azure blob, it is systematicaly happening on big volume of data ( 100 million rows).
On smaller size we dont hav ethe issue. have you find in between some workarounds?
Thanks,
Joseph
Hello,
We had the same issue in SAP BODS SP12, but it had impact only on 1 or 2 percent of jobs and was not critical for dataflow. After SAP BODS upgrade to SP14 80% of jobs are impacted.
Have you found a RCA of this issue: HTTP client error:<56>:<Failure when receiving data from the peer>?
Thank you.
Did you discuss with SAP before upgrade? we are also facing same issue and SAP suggested to upgrade but we never done since no concrete answer from SAP.
We're using sps8 and jobs will fail randomly 1 or 2 weekly or monthly once more over this is nothing to do with upgrade,
try to check your parameters related to connectivity, network and file size, etc.
DS can open the same file in write mode within a process only once each time. A File location, like Azure Blob, used in a file reader will open a file in write mode in the local folder specified in the File Location.
It will download the file from Azure Blob. Then, it will reopen the local file in read mode and start processing the file.
If all DF using the reader with the same File Location are running sequentially, then the same File Location in a reader can be used multiple time in the same Job.
If WF containing the DF using the reader with same File Location are running in parallel. They will try to open the local file at the same time leading to the error.
2737777 - Error: "HTTP client error:<56>:<Failure when receiving data from the peer>" happens randomly in DS jobs with Azure data source.
