Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Thank you!

That resolved the issue - thanks for the quick response and for making such a useful tool!

Re: Archive corrupted when replacing existing file

Remove the -resume switch. You cannot use it for a regular transfer. The switch is intended to resume a previously interrupted transfer only.

Archive corrupted when replacing existing file

I use WinSCP to automatically download zipped backups of a hosted database.

If a file already exists on the local file system, using WinSCP to download and replace it with a newer version gives me the following error message when I try to extract the file using 7-Zip:
There are some data after the end of the payload data : <filename>

Noticed originally on 5.13.1, still happens on 5.13.3.

Deleting the local file and re-running the script (either manually or automatically) works correctly - the downloaded file can be extracted as normal.

I have tried manually setting the transfer type to each of the 3 options (binary, ascii, automatic) with no change in behavior.

Backup script:
open ftpes://site:password@ip -certificate="scrubbed"

lcd C:/path/to/local/backup/dir/
get -resume -neweronly /path/to/backups/*.gz

Windows 10 Pro scheduled task:
C:\Windows\System32\cmd.exe /c /ini=nul /script="c:/path/to/script.txt"