Thank You for the response.

We have now upgraded our application to WinSCP 5.7.4. I will keep posted if we get any other problems in new version.

Thank You,
Viral

Try upgrading to the latest version of WinSCP first.

Thanks for replying.

In fact, we already have increased the timeout from 15 seconds to 60 seconds. However, this occurred again twice after increasing the timeout.

Pleas give any suggestions...

Should we increase the timeout more than 60 seconds?

Thank You,
Viral

If this happens rarely, if can be due to a temporary overload of the server. Did you try increasing Session.Timeout?

This is not the bug you refer to:
https://winscp.net/tracker/996

If it were, it would not work at all, not only rarely.

We are using c# winscp.net assembly.

We have set up the task scheduler job which runs every 10 minutes.

The task failed 4-5 times in around 3 weeks time. The task failed because of this error

"WINSCP.TimeoutException: Timeout waiting for WinSCP to respond - WinSCP has not responded in time (response log file C:\Users\User\AppData\Local\Temp\wscp1.tmp was not creataed). This could indicate lack of write permissions to the log folder or problems starting WinSCP itself. at WinSCP.session.CheckForTimeout(String additional) at WinSCP.session.open(sessionoptions sessionoptions) at WIBSFile.download.login."

Note - We have checked the permissions on the log folder. this task is running under admin account so there is no permission issues.

WinSCP version 5.5.2 - it says that the issue was fixed in this version.

However, we are using the 5.5.6 version and this problem occurs in this version.

Any quick help will be highly appreciated.

Thank You,