Web Activity gives Error Code 2108....but same API call works fine in Postman

Paul R 96 Reputation points
2021-04-20T03:47:40.47+00:00

I've searched forums for days, but cannot find answer to this problem.

*I have a simple GET API call that works fine in Postman, but my Web Activity fails with Error Code 2108:

Error calling the endpoint 'https://app.triblio.com/api/reports/account_metrics'. Response status code: ''. More details: Exception message: 'The format of value '1618415703' is invalid.'. No response from the endpoint. Possible causes: network connectivity, DNS failure, server certificate validation or timeout.

*The error refers to value '1618415703', which a header item called date. The value is a Epoch Timestamp. (that value is from a few days ago, but still works fine in Postman. When I use current Epoch Timestamp, I get the same error).

*There are three headers required to authenticate: date, token, and signature. When I remove one of those headers, I get an "Unauthorized" error....so I know that it is connecting to the URL successfully.

*Per other forum suggestions, I have increased the timeout but I think that is unrelated because the Web Activity fails almost instantly. In Postman, the API calls takes 3 seconds to run.

*I have also experimented with adding in a Linked Service that calls that same URL, but that didn't seem to make a difference.

Thank you for any help; I'm watching for replies so that I can respond quickly to follow-up questions.

89362-code.txt

89310-error-message.png

89308-web-activity-pipeline.png

89306-postman.png

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
{count} votes

Answer accepted by question author
  1. Paul R 96 Reputation points
    2021-04-28T03:55:44.677+00:00

    Himanshu wrote me and said:

    "We did had discussed internally this issue and we aggreged that mostly the header is passed as string in WebActivity whereas Postman it is integer/long."

    Conclusion: it appears that WebActivity is doing something to a piece of data that I don't intend for it to do (treating it as a string).

    I'm going to close this issue because it doesn't seem like there's a way to get around this problem in Web Activity. Personally, my workaround will be to make the API call using Powershell, and I'll call that Powershell script from within Data Factory.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Jagjeet Singh Makhija 10 Reputation points Microsoft Employee
    2023-03-03T19:20:07.3433333+00:00

    Most of us face this err while try to open URL:

    User's image

    Above issue is resolved now we can easily pass the cookie values from one web component to another web component using Azure Data Factory below is the screenshots to demonstrate.

    Passing Web2 component cookie values to Web3 component.

    Need to set this in the header section with the given expression.

    User's image

    Set the reference of cookie values in Web2 component.

    User's image

    Passed the reference of cookie values to Web3 component and attach with the given URL section in settings.

    User's image

    Below URL accessed using cookie value passed to this Web3 component.

    User's image

    Hope this will help Azure community to fix this issue.

    Article published by - Jagjeet Makhija

    2 people found this answer helpful.

Your answer

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