Filesize does not match

Hello,
I am trying to automate a SFTPfile transfer using WinSCP. I created a script, but when it runs the file sizes do not match. Please refer to the attached document.

Please let me know what I am doing wrong.

Thank you,
Brady

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

Hi Martin attached is my batched file.

martin wrote:

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

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. 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.

Hi Martin,

Attached is the log. Please refer to 2/22.

Thank you for the help.

When I was going through the logs I saw the attached. Its weird that it sees the file size is 894,155,824 but only transferred 202,464,144.

I do not see any problem in the log.
Can you upload the file correctly using any other (even GUI) SFTP client?

martin wrote:

I do not see any problem in the log.
Can you upload the file correctly using any other (even GUI) SFTP client?

Thank you for the reply Martin, it works when I just run the batch file. I am trying to run this through Task Scheduler. I have this batch file being triggered every weekday at around 7:30. When this happens I see a difference in the file sizes, but say I create a one time task to trigger at 8:00 on the same day it works. So I thought it might be a timing thing, so I changed the weekly task to 8:00 as well and still saw a difference in file sizes.

Have you run into this issue before or anything similar? I am thinking it might be an issue on the sftp server, but genuinely do not know.

Thank you,
-Brady

Can you attach log files on level "Debug 1" for comparable attempts, one working and one failing?
First, please add a ls command to the script after the upload.

martin wrote:

Can you attach log files on level "Debug 1" for comparable attempts, one working and one failing?
First, please add a ls command to the script after the upload.

Hi Martin,

The reason I did not reply until now was because it was actually working the last few weeks. On Thursday, Friday and today I started seeing the same issue again. Attached is my log and bat file. 3/13 is an example of a day it worked. The other dates are examples of dates they did not work.

In regards to my batch file I want to add the Debug level 1 and 1s command. I am not familiar/the best with winscp. Can you look at my bat file let me know what I am doing wrong when trying to add these?

I appreciate the help as always.

Thank you,
Brady

bhenson wrote:

In regards to my batch file I want to add the Debug level 1 and 1s command. I am not familiar/the best with winscp. Can you look at my bat file let me know what I am doing wrong when trying to add these?

1) It's ls, not 1s.
2) The log file does not look like the session was started using that batch file anyway. There's no /loglevel, nor 1s (sic).

martin wrote:

bhenson wrote:

In regards to my batch file I want to add the Debug level 1 and 1s command. I am not familiar/the best with winscp. Can you look at my bat file let me know what I am doing wrong when trying to add these?

1) It's ls, not 1s.
2) The log file does not look like the session was started using that batch file anyway. There's no /loglevel, nor 1s (sic).

Thank you for the quick reply.

Correct, the logs were taken before I added /loglevel and ls. I was just wanting to verify I was adding these to the correct location. I changed 1s to ls. Does everything else look good?

Thank you again.
-Brady

Look good. So once you reproduce the problem with this setup, please attach log files for comparable attempts, one working and one failing.