I just started having an issue pulling a file from an SFTP site. This issue started just after the WinSCP software was updated to the latest version (as of a couple weeks ago) from a much older (unknown) version.
Description of the process.
I am calling WinSCP.com from a SQL Server Integration System package in order to either pull a full SQL backup file or a differential backup file depending on the day of the week. The full backup is downloaded one day a week (friday) because it is > 11gb and takes over 3 hours to download. The previous issue we had was that a connection issue would occur during this time and the process would error out and quit. After upgrading to the latest version of WinSCP when the connection issue occurs the process reconnects and starts the download from the beginning. This is an issue because we have had this job run for more than a day and a half on the weekend before it finally errored out. This same process occurs for three similar jobs that each have an 11+gb file. Each of these jobs has been reporting the issue where the download will start at the beginning when the connection breaks and restarts.
1. Is there a setting that can reconnect and not start the download from the beginning?
2. If #1 is not possible, is there a better combination of settings that can be used to better accomodate connection issues? Via automation?
I have attached the log file that was created this past Friday night. I have obfiscated the file paths, site, and user/password names. As you can see it downloads 99% of the file and times out. It then attempts to reconnect or maybe it downloads again until it gets to 99% (that part isn't clear to me since there are no timestamps). It then shows that it errors out at 19%, meaning it started to download the file from the beginning.
Thanks for your help.
Transfer protocol: SFTP
Windows: 10 Enterprise