We have a Powershell script which opens a Winscp session to remote FTP server. The script has been scheduled in task scheduler to trigger at 5 schedules in a day. Occasionally, the script that triggers at 5 AM fails with the following message in the log file. But the other schedule runs are not impacted.
Timeout waiting for WinSCP to respond - WinSCP has not responded in time (response log file C:\Users\taskrunner\AppData\Local\Temp\wscp1008.03EE7DB9.tmp was not created). This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.
We have investigated the logs on the server and couldn't find anything that could lead to this failure. I have also searched for this error in this forum and understood that this was identified as bug and has been fixed in later versions prior to v 5.7.
Could you advise how to investigate and find the root cause of this ?