Share via

Azure Data factory got error when getting information from HubSpot

Simon TC Kong (Tricor HK/IT) 6 Reputation points
2021-06-03T06:36:00.833+00:00

Encounter problem suddenly when preparing data from HubSpot

error message:

Operation on target ForEach_Table failed: Activity failed because an inner activity failed; Inner activity name: Copy_HubspotTBL, Error: Failure happened on 'Source' side. ErrorCode=UserErrorOdbcOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][Hubspot] (100) Error parsing JSON: Invalid value. while parsing string <html>
<head><title>414 Request-URI Too Large</title></head>
<body>
<center><h1>414 Request-URI Too Large</h1></center>
</body>
</html>
.,Source=Microsoft.DataTransfer.ClientLibrary.Odbc.OdbcConnector,''Type=System.Data.Odbc.OdbcException,Message=ERROR [HY000] [Microsoft][Hubspot] (100) Error parsing JSON: Invalid value. while parsing string <html>
<head><title>414 Request-URI Too Large</title></head>
<body>
<center><h1>414 Request-URI Too Large</h1></center>
</body>
</html>
.,Source=HubspotODBC_sb64.dll,'

Any method to find which item is too large ?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,687 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. KranthiPakala-MSFT 46,487 Reputation points Microsoft Employee
    2021-07-15T20:07:11.923+00:00

    Hi All,

    Below is the summary of the support request. Just sharing it here incase anyone else experience this issue:

    Symptom:
    Operation on target ForEach_Table failed: Activity failed because an inner activity failed; Inner activity name: Copy_HubspotTBL, Error: Failure happened on 'Source' side. ErrorCode=UserErrorOdbcOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][Hubspot] (100) Error parsing JSON: Invalid value. while parsing string
    414 Request-URI Too Large

    Resolution:
    After investigating on this issue with our Driver team they have updated with the below details:

    For Table "Contact_Properties_Values" :
    To fetch all the properties for a contact, there is a prerequisite to append the property in the request Url itself.
    If such a method is not followed, it's not guaranteed that the expected properties would be returned from the server.
    Currently it is by the design of the particular endpoint used by the table contact_Properties_Values, so no other table faces this issue, but contact_Properties_Values is effected by 414 error, which is for URL being too long.

    As suggested by Driver team, recommended user to check with Hubspot to understand what is the maximum Url length being supported and any enhancements that can be done by them to overcome such issues.

    Hope this info helps.
    Thanks

    0 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.