Error Sending file to SFTP Server

Advertisement

gdswll
Joined:
Posts:
3
Location:
Virginia

Error Sending file to SFTP Server

I'm getting the error Software caused connection to Abort but I'm unsure as to why I'm getting it. The process runs and creates a 0KB file on the SFTP server but then it times out. The file I'm attempting to load is 31KB. The log file shows that it reaches 30KB, then it stops. I've tried turning of the Optimization buffer with the same results. Below are the Raw Settings i used in the SessionOptions but none of those helped.

sessionOptions.AddRawSettings("PingIntervalSecs", "5");
sessionOptions.AddRawSettings("PingType", "2");
sessionOptions.AddRawSettings("SendBuf", "0");
sessionOptions.AddRawSettings("SshSimple", "0");

Any assistance would be greatly appreciated. I'm using the .Net Assembly WinSCP Version 5.13.7 Build 9125
Description: Transfer log
Description: Code used to upload file

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
40,567
Location:
Prague, Czechia

Re: Error Sending file to SFTP Server

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, set Session.SessionLogPath. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

gdswll
Joined:
Posts:
3
Location:
Virginia

Error Sending file to SFTP Server

Here are the requested log files
  • Sessionlog_20190221084358.txt (607.95 KB, Private file)
  • Debuglog_20190221084354.txt (285.78 KB, Private file)

Reply with quote

gdswll
Joined:
Posts:
3
Location:
Virginia

Re: Error Sending file to SFTP Server

I set the SendBuff to 0 and now the file is being uploaded successfully, very strange since I had that set before and received the same error. I'm beginning to suspect that it may have been an issue on our network side as some work was done on that over the weekend. I'll continue to monitor and if it errors out again I'll append the code and associated logs to this thread.

Thank you for your assistance on this

Reply with quote

Advertisement

You can post new topics in this forum