Failed to execute delete activity with data source 'Sftp' and error 'Meet network issue when connect to Sftp server 'sftp.xx', SocketErrorCode: 'ConnectionReset'.

Question

It says "An existing connection was forcibly closed by the remote host'.
kindly let me know how to rectify this error.

Answer 1

Hi @Siddharth Srinivasan ,

Welcome to Microsoft Q&A platform and thanks for using Azure Services.

As I understand your issue in SFTP connection, could you please try below options:

• The issue might be due to Firewall.
  If you are using Azure Integration Runtime, then you could choose to add Azure Integration Runtime IPs into the allow list.
  if you are using Self Hosted Integration Runtime (SHIR) on either source or sink and if the access is restricted to IPs that are whitelisted in the firewall rules of your SFTP, then could you please make sure to whitelist the IP address of the machine that hosts your SHIR.

Link for Azure IP Ranges and Service Tags

• The number of Max concurrent connections to your SFTP server could be another reason. Could you please check what is the maximum concurrent connection limit to your sftp server? Based on that please set your sink Max concurrent connection less than the SFTP concurrent connection limit set by SFTP admin.

Hope this will help. Please let us know if any further queries.

------------------------------

• Please don't forget to click on or upvote button whenever the information provided helps you.
  Original posters help the community find answers faster by identifying the correct answer. Here is how
• Want a reminder to come back and check responses? Here is how to subscribe to a notification

Answer 2

This pipeline runs every hour copying files from SFTP to datalake and once the copying completes, the data from the sftp is deleted.
It has been in use for more than a year but suddenly from the past 2 weeks, randomly we are getting this error.
I don't think it can be the firewall, as that should cause errors in all the runs, shouldn't it?

Kindly help me investigate the issue @ShaktiSingh-MSFT