I have a console app (VB.NET) very similar to the example code presented on this site. When run interactively, it can upload/download via SFTP without issues. When run via a Scheduled Task, it runs silently without issues. However, when my RDP session to the server disconnects, the Scheduled Task runs, but WinSCP fails with error messages like this:
The WinSCP executable appears to have crashed. Log file C:\Documents and Settings\MyServiceAccountName\Local Settings\Temp\tmp112F.xml does not exist.
Other times, the WinSCP.exe and WinSCP.com processes stay running and idle until I kill them.
Is there something special about running WinSCP from a console app running as a scheduled task that would cause this type of behavior?