RajasThakur-7366 avatar image
0 Votes"
RajasThakur-7366 asked RajasThakur-7366 commented

Pipeline failing with Error code: 2010 / Failure type: User configuration issue / Details: Processed HTTP request failed.

I am getting this error in Azure data factory. Please refer the screenshot below:202551-image.png

I tried to find similar issues to this one but didn't. It seems like a one off error because when we rerun the pipeline, we don't get this error again.
If it is of any help, we are getting this error through a 'Get Metadata' or 'Lookup' block. Both of these blocks are inside a 'ForEach' block.

Any possible reason as to why we are encountering this issue? We haven't made any changes from our end to the existing pipelines. We first got this error on 13th May and then on 15th May

image.png (12.8 KiB)
· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @RajasThakur-7366 and welcome to Microsoft Q&A.

Given how this was a one-off, and with details like "Processed HTTP request failed" , I'm thinking something along the lines of a router hiccuped. I wouldn't worry about the "User configuration issue" just yet. I would pay more attention to the "user configuration issue" if this was a web activity, as you are closer to the actual request there. For the Lookup and Get Metadata, the Factory creates the request behind the scenes based upon your input. So for the request to fail, either something went wrong behind, or your found some edge case not caught by other error codes. Given how it did not happen on repeat, I'm thinking not the edge case.

I can take a look through my resources if you like, this was just my off the cuff opinion.

1 Vote 1 ·

Hello @MartinJaffer-MSFT ,

Thank you for your reply and initial analysis.

I would really appreciate if you can look through your resources for any case similar to this and what might be a possible reason for this issue.

We have a pipeline running for multiple tables. Whenever we have faced this error, it is not necessarily for the same table. When we just rerun the pipeline, it doesn't occur on the consecutive run.

Let me know if you need any additional details from my end. The last time we got this error was on 17th May around 12:00 PM CST.

0 Votes 0 ·

Okay, I haven't found any matches so far in my troubleshooting guides. The most similar cases I found were Error Code 2012 , and Error Code 2108 An error occurred while sending the request. Both of these required deep investigation.

Thank you for letting me know this isn't a 1-time occurrence , but an intermittent problem. More than one point is needed to determine a pattern. With this knowledge I can direct you to someone who can look into the back end logs for a deeper investigation.

In case you do not have a support plan, I will be sending you directions in a private message on what I need to give you a 1-time free support ticket.

If you do have a support plan, you can open a ticket by finding your Factory in the Azure Portal, and scrolling to the bottom of the side-bar to find "New support request" under "Support + troubleshooting" as seen in below picture.


Either way, please let me know the ticket number.

Thank you for your patience @RajasThakur-7366
[1]: /answers/storage/attachments/203790-image.png

0 Votes 0 ·
image.png (89.8 KiB)

Oh, I did find one more case, but it was coming from an odd angle. It had a very different error code, but similar message. In that case, someone was calling 100 simultaneous runs of a Databricks notebook from Data Factory. The error was because of the heavy load this put on Databricks. I don't think this applies to you, but could you tell me whether there is much parallel activities / loop / pipelines happening?


0 Votes 0 ·
Show more comments

Hello @RajasThakur-7366,
We haven’t received any email from you as requested in the last response and was just checking back to see if you have a resolution . In case if you have any resolution please do share that same with the community as it can be helpful to others . Otherwise, please respond back with the more details as requested and we will try to help .


0 Votes 0 ·

Hello @MartinJaffer-MSFT ,

We haven't encountered this issue since last week and feel that it must've been a transient issue.

In case if this occurs again, I can update about it.

Thanks for all your help. I really appreciate it.

Rajas Thakur

0 Votes 0 ·

0 Answers