How to fix Error COPY TO SYNAPSE

Aura Viviana Duarte Hernández 20 Reputation points
2023-07-13T17:07:27.8666667+00:00

User's image

User's image

User's image

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,186 questions
{count} votes

Accepted answer
  1. KranthiPakala-MSFT 46,602 Reputation points Microsoft Employee
    2023-07-14T00:24:47.5266667+00:00

    @Aura Viviana Duarte Hernández Welcome to Microsoft Q&A forum and thanks for reaching out here.

    Error details: ""message": "ErrorCode=FailedToGetAccessTokenByMl, Failed to get MI access token. The error message is: One or more errors occured

    Request MI token failed: Failed to get service token from ADF service with key IR@41xxxxxxxxxx, time cost is: 0.2812287 seconds, the error code is: UnexpectedFauIt, activityld is: a01c75fd-cdb3-440e-bb81-6357b1206f1f and detailed error message is An error occurred while sending the underlying connection was closed: Could not establish trust relationship for the SSL/TLS. The remote certificate is invalid according to the validation procedure"

    From the error message and the image, you have shared, my understanding is that the issue is not consistent, and it seems like a transient issue. All your Copy activities inside forEach ran successfully except this failed run and because of which the forEach is marked as failed and hence the pipeline. Please correct me if my understanding is not accurate.

    As per the error message it seems like it is caused by a transient network issue between the self-IR machine and ADF service while trying to get the MI access token from ADF service. Since you are doing a forEach in parallel, sometimes this network issues may happen as multiple concurrent network requests from SHIR machine to ADF service may be interrupted/throttled. Whereas if you do a forEach in sequential, you may avoid this problem.

    Solution: Since this seems to be transient network issue, I recommend implementing retry mechanism in your copy activity, so that if something goes wrong or any transient network issue occurs for any particular iteration, then the copy activity retries as per the copy activity retry configuration.

    User's image

    But if you notice this behavior frequently, then I recommend filing a support ticket with network team, as the issue resides more of your SHIR networking and Azure ADF networking side. For that they might need lot of network logs from your end to troubleshoot and identify the problem.

    Hope this info helps. Do let us know how it goes with retry configuration.


    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Aura Viviana Duarte Hernández 20 Reputation points
    2023-07-14T01:13:44.5766667+00:00

    Hello @KranthiPakala-MSFT

    Thank you for you answer, realized change with the recommed "recommend implementing retry mechanism in your copy activity".

    I confirm if it worked tomorrow, apply to those who only failed. Since I have several processes with the for each. I appreciate your collaboration!

    User's image

    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.