I have the same problem.
The error is:
WinSCP.SessionLocalException: WinSCP process terminated with exit code 3 and output "", without responding (response log file was not created). This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.
But it only occurs when I run it via Task Scheduler.
The funny thing is that it runs with no problem when I start it manually. Same user logged in that runs scheduled task. Same application. The only difference is that running through task scheduler gives me error.
Running on Windows Server 2008 R2 Standard.
I have already tried versions 5.1.7 and 5.2.6.
Compatibility mode makes no difference.
Can you help?
one more observation
If in task properties on General
tab in Security options
I set the radio to "Run only when user is logged in"
– no error.
"Run whether user is logged on or not"
Friend told me that it happens because WinSCP requires User Environment. He suggested that to solve it I should use SSH Stack instead of sending parameters to application.
I don't really know what that means, but maybe it will help you out.