Q: SFTP Connection errors 10054 (0x2746). Is there something we can look at in regards to this error? What causes it and if we can resolve? We’ve encountered a situation twice now where a vast amount of rules appear to stop processing to 1 particular server. The rules in web remote all turn green and stay green as if they are currently being triggered, but there is no output on the runtime log and no transfers take place. To resolve the issue we’ve restarted the Limagito server, and rule processing occurs normally again. Are we able to provide you with some logs that might help shed light on what’s occurred?
We have 173 rules, and of the failures they seem to be with this 1 SFTP server, destination and source rules. Is there a preference in which one we use? We scan the rules every 70 seconds.
- With our SFTP Source Code Vendor 1 (SB) the error message looks like:
6/3/2022 9:12:57 AM SFTP Connected Error
6/3/2022 9:12:57 AM Connect attempt 1 Exception: Connection lost due to error 10054
6/3/2022 9:12:57 AM Connecting SFTP Server..
6/3/2022 9:12:57 AM Cyclus [SFTPGET]
6/3/2022 9:12:57 AM Start Source Thread
- With our SFTP Source Code Vendor 2 (CK) the error message looks like:
A: With 70 seconds scan time we would certainly enable the ‘Stay connected’ option (Common Tab of SFTP setup). We guess this SFTP server is no longer accepting new connections (after x time). Please also check the ‘Hint’ in the feedback when using our SFTP Source Code Vendor 2 (CK). If you trigger the rules often then some SFTP servers will find this (connects/disconnects) suspicious and will no longer allow new connections for a certain time.
- SFTP Setup (Source or Destination), enable ‘Stay Connected’.
#SFTP #Filetransfer #Filemanagement
If you need any info about this ‘ SFTP Connection errors’ question, please let us know.