none
ADF V2 - Intermittent Error Eventually Resolves Itself "The remote name could not be resolved"

    Question

  • My pipeline can fail at any point with the following error.  I can restart a couple times and eventually it succeeds.  Any ideas as to what this might be?  It says it is user error and it points to an activity but eventually (after restarting the pipeline), it gets past that point and it may fail at a totally different point with the same message "The remote name could not be resolved" or it might just succeed altogether.  DTU's and memory usage are not being maxed out.  Any suggestings?

    { "errorCode": "BadRequest", "message": "'Type=System.Net.Http.HttpRequestException,Message=An error occurred while sending the request.,Source=mscorlib,''Type=System.Net.WebException,Message=The remote name could not be resolved: 'eu.frontend.clouddatahub.net',Source=System,'", "failureType": "UserError", "target": "Load Table" }


    ml

    Monday, August 20, 2018 8:41 PM

All replies

  • The errors look to happen when integration runtime fails to connect to the data transfer server. Are you using integration runtime in this pipeline? Maybe you can check the network environment of the integration runtime.
    Tuesday, August 21, 2018 7:31 AM