Winscp Software Caused Connection Abort

Posted : admin On 9/20/2019
Active4 months ago
  1. Winscp Software Caused Connection Abort
  2. Reason Winscp.sessionremoteexception Network Error Software Caused Connection Abort
  3. Sftp Network Error Software Caused Conne…

Winscp Software Caused Connection Abort

Oct 19, 2007  WinSCP’s 'Network error: Software caused connection abort' Message is Driving Me Crazy! Lowell Heddings @lowellheddings October 19, 2007, 5:17am EDT WinSCP is by far and away the best SCP/SFTP client for Windows users, but the default settings don’t use keepalive, so you get disconnected far too often. 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.

'Network error: Software caused connection abort' when trying to remote into my Linux machine from my Windows XP one today. Nothing has changed on my end since I last came in (last week). All of the sudden I can't log into the Linux computer (and I need to) through WinSCP or Putty. Does anyone know why this is? But, when I try and use PuTTY to log into server PuTTY does not connect and gives the “Network error: Software caused connection abort” message. What am I screwing up? In particular, this can occur even if you didn’t do anything, if you are using SSH-2 and WinSCP attempts a key re-exchange. The problem can be caused also by the firewall. Try to disable it temporarily to see if the problem persists. Refer to FAQ. It can also occur if you are using keepalives in your connection. Having an issue with all new re-imaged machines (Win7 Pro SP1) when trying to use any FTP client (FileZilla and WinSCP). Every time the user or my domain account is logge. SOLVED Network error: Software caused connection abort - FTP - FileZilla/WinSCP - Windows 7 Forum - Spiceworks - Page 2.

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:

Reason Winscp.sessionremoteexception Network Error Software Caused Connection Abort

a) Added an exception to windows firewall to allow winscp through.

b) Enabled 'Executing dummy protocol commands' under Keepalives in WinSCP Advanced Site Settings

Free

2018 vehicles with awd manual transmission

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)

If anyone is familiar with how to fix this issue please let me know. See log entry and powershell screenshot attached.

emalcolmb
emalcolmbemalcolmb

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.

Sftp Network Error Software Caused Conne…

emalcolmbemalcolmb

Not the answer you're looking for? Browse other questions tagged sftpscpwinscp or ask your own question.

Active4 months ago

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)

If anyone is familiar with how to fix this issue please let me know. See log entry and powershell screenshot attached.

emalcolmb
emalcolmbemalcolmb

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.

emalcolmbemalcolmb

Not the answer you're looking for? Browse other questions tagged sftpscpwinscp or ask your own question.