Winscp Software Caused Connection Abort
- Winscp Network Error Software Caused Connection Abort Authentication Failed
- Winscp (efatal) Network Error Software Caused Connection Abort
- Network Error Software Caused Connection
Winscp Network Error Software Caused Connection Abort Authentication Failed
I have a scheduled job to perform secure file transfers daily through WinSCP. The flow starts with 2 ssrs file share subscriptions which drops 2 files in a local directory. Then the sql server agent job I scheduled kicks off a powershell script which initiates the winscp sftp transfer of the 2 files to the remote SFTP server.
The job and file transfers were all working fine and dandy for 2 months until randomly last week when the job started failing on some days (but not others). The logs show a cryptic network error 'Software caused connection abort'. I've checked winscp's support docs here https://winscp.net/eng/docs/message_software_caused_connection_abort, here https://winscp.net/eng/docs/message_unexpected_close here https://winscp.net/eng/docs/faq_connection_refused and other sources here https://www.hostingride.in/content/solved-network-error-software-caused-connection-abort-winscp-error-putty-keepalives
Every server identifies itself by means of a host key; once WinSCP knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine. If you see this message, it means that WinSCP has not seen this host key before, and has no way of knowing whether it is correct or not. Putty software caused network abort. Software caused connection abort'. It also happens when trying to connect WinSCP on the same PC. If I try on my desktop. Firstly i apologize my English. Our Azure Linux(Ubuntu 16.04.2 LTS) instance has been running for more than a 2 months now. Suddenly tuesday night without any configuration to server, I get randomly 'Software caused connection abort' from my automated powershell-script. Script uses Winscp-client for sftp-connection.
Based on suggestions found I:
a) Added an exception to windows firewall to allow winscp through.
b) Enabled 'Executing dummy protocol commands' under Keepalives in WinSCP Advanced Site Settings
c) Increased the server response timeout and seconds between keepalives to 360 seconds each
Winscp (efatal) Network Error Software Caused Connection Abort
None of these fixed the problem. And oddly the file transfer is not consistently failing every day. Running the job repeatedly (same code) fails usually but occasionally succeeds (see powershell screenshot attached)
If anyone is familiar with how to fix this issue please let me know. See log entry and powershell screenshot attached.
1 Answer
Answer: Being that this was a server-side issue, this item has no immediate solution. The solution is to confirm with the other party that their SFTP server is configured properly becuause the client-side requests are being initiated properly.
Not the answer you're looking for? Browse other questions tagged sftpscpwinscp or ask your own question.
I have a scheduled job to perform secure file transfers daily through WinSCP. The flow starts with 2 ssrs file share subscriptions which drops 2 files in a local directory. Then the sql server agent job I scheduled kicks off a powershell script which initiates the winscp sftp transfer of the 2 files to the remote SFTP server.
The job and file transfers were all working fine and dandy for 2 months until randomly last week when the job started failing on some days (but not others). The logs show a cryptic network error 'Software caused connection abort'. I've checked winscp's support docs here https://winscp.net/eng/docs/message_software_caused_connection_abort, here https://winscp.net/eng/docs/message_unexpected_close here https://winscp.net/eng/docs/faq_connection_refused and other sources here https://www.hostingride.in/content/solved-network-error-software-caused-connection-abort-winscp-error-putty-keepalives
Based on suggestions found I:
a) Added an exception to windows firewall to allow winscp through.
b) Enabled 'Executing dummy protocol commands' under Keepalives in WinSCP Advanced Site Settings
c) Increased the server response timeout and seconds between keepalives to 360 seconds each
None of these fixed the problem. And oddly the file transfer is not consistently failing every day. Running the job repeatedly (same code) fails usually but occasionally succeeds (see powershell screenshot attached)
Windows vista home key. Aug 25, 2009 Hi again I m gonna give you something which is only for windows vista users many of you don't like to buy an original copy windows then this is the best way to get you activated your windows but I want to tell every user that don't support piracy instead of that buy that product because the product bought pirated are some time fake and sometime they don't work.
If anyone is familiar with how to fix this issue please let me know. See log entry and powershell screenshot attached.
1 Answer
Answer: Being that this was a server-side issue, this item has no immediate solution. The solution is to confirm with the other party that their SFTP server is configured properly becuause the client-side requests are being initiated properly.