Although I like WinSCP very much it seems to disconnect and reconnect for me every 15 seconds as other posts have noted.

I found that, oddly, if I clicked the speed limiter dropdown and left it down, the disconnections didn't happen at all. However the transfer speed slowly dropped away to a couple of hundred bytes/sec.

I hope that may offer some kind of clue as to what is happening...ahh, maybe it is just that selecting the speed limiter pauses the transfers altogether...back to the drawing board.

OK so when all else fails read the manuals...

as mentioned in this post https://winscp.net/eng/docs/message_disconnected it seems to have totally solved the issue - running the two command lines at the bottom of this page:

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd421710(v=ws.10)

did the trick. Hasn't stopped since.

davids wrote:

Martin, in the first log message, which "Software" is it referring to? Is that WinSCP? I understand that these two messages are saying that the transmission was interrupted, but is there any way to know which end caused the interruption?

The "software" here usually means "Windows OS", see
https://winscp.net/eng/docs/message_software_caused_connection_abort#middle

Well, I may have spoken too soon...

I've confirmed that the remote side has configured to not touch the file until it has been present for 5 minutes - which should be plenty of time to transmit.

And some of the time that works.

But other times it starts transmitting, then just seems to stop, and then I get the same messages in the log:
Network error: Software caused connection abort
Fatal error while disposing the SFTP queue

Martin, in the first log message, which "Software" is it referring to? Is that WinSCP? I understand that these two messages are saying that the transmission was interrupted, but is there any way to know which end caused the interruption?

Thanks!

Thanks for your feedback.

This was a case of "if something seems to be the case, keep digging even if people say it isn't".

Turned out to be an out-of-control process on the remote side. The process was intended to move files out of the destination folder to be processed. It was SUPPOSED to only move a particular filename (ignore all others), and also to only even look for files every five minutes or so.

The reality was it would move any file it found, and it would start trying to move the file about 19 seconds or so after it appeared! So what was happening was this:
1. We start transmitting the file, causing the file to appear in the destination folder.
2. The remote side immediately (within 19 seconds or so) moves the file fragment to another location.
3. Our session, seeing the target file suddenly gone, assumes the connection was broken, and it attempts to reconnect.
4. That was successful, so file transmission continues.
5. The file disappears again
6. and so on.

After we got the remote site to leave the stupid file alone and let us transmit it, it started working perfectly!

Sorry, I have no idea, what the problem can be.

Martin, now it seems even worse... After I upgraded to 5.8.3 RC, I had a transmission that took 1.5 hours to send a 97k file, with 201 disconnections!

Log attached (private)

martin wrote:

Can you try to upgrade to 5.8.3 RC?

I've upgraded to 5.8.3 RC, but I won't have results until tomorrow.

Can you try to upgrade to 5.8.3 RC?

Another question I have is if there is any way to determine why the command line transfer of the file is taking so long in the first place? I tried copying the same file from the GUI, and it appeared to copy in less than a second with no problem at all.

I have a file that I transmit to a remote server daily, and have done so for about 6 months. It seemed to work fine for a while, but just lately I'm having a real problem with the connection dropping and reconnecting, about every 19 seconds! I assume the file has been increasing in size, it is now about 93K.

I'm not aware of any changes on our side, other than routine updates from Microsoft. I have no visibility into changes to the remote server.

I'm hoping someone can help with this, it is causing errors in the copied file, and I'm losing hair rapidly!

I've attached a full log.

Here are the logged errors that repeat each time:
Network error: Software caused connection abort
Fatal error while disposing the SFTP queue.
Connection was lost, asking what to do.
Asking user:
Software caused connection abort ()
Network error: Software caused connection abort

WinSCP version: 5.7.5
Windows version: Server 2008 R2
Transfer protocol: SFTP
Automation (command in log)