Discovery wrote:

Im facing the same problem. My script also seems to start moving file to new destination before its completed at source location. Im using "option batch continue" with parameters -delete -resume and -neweronly.

Im sure WinSCP wait for a file to completly download and after that it start moving file to new destination. Is it like this ? any suggestion to fix this problem.

Your duplicate post:
https://winscp.net/forum/viewtopic.php?t=26280

WinSCP version is 5.11.
this problem is with few files out of hundreds.
Do I have to increase the -timeout value also.

Thanks and regards.

hi martin,

Im facing the same problem. My script also seems to start moving file to new destination before its completed at source location. Im using "option batch continue" with parameters -delete -resume and -neweronly.

Im sure WinSCP wait for a file to completly download and after that it start moving file to new destination. Is it like this ? any suggestion to fix this problem.

Thanks and regards.

Trashcan wrote:

I am using live-synchronisation. Could it be that WINSCP is already transferring the file while the file to be transferred is not yet complete, causing an empty file in the destination folder?

Well, if some files are incomplete (but not empty), it can be the case. But if they are either empty or complete, it doesn't sound likely.

Is it possible with WINSCP to automatically synchronise files between locations at set time intervals?

Please read documentation:
https://winscp.net/eng/docs/guide_schedule

Hello,

I am using live-synchronisation. Could it be that WINSCP is already transferring the file while the file to be transferred is not yet complete, causing an empty file in the destination folder?

Is it possible with WINSCP to automatically synchronise files between locations at set time intervals?

Thanks and regards.

Hello,

I have the same problem. I am using live-synchronisation and have empty files at the destination folder. Any idea of the cause?

Regards.

Some servers fail to report an error when destination disk is empty and create an empty file instead. Can this be your case?

I've been using WINscp for years now, always moving large files to our Moodle site. In the last few weeks, when I've transferred folders across they appear in the destination incomplete, some files completely empty