WinSCP process terminated with exit code 3. There was no output.

Hi, everyone!

Been running the .NET version for years. Recently though we have been getting the following error:

WinSCP process terminated with exit code 3. There was no output. Response log file C:\Windows\TEMP\wscp1688.019FD045.tmp was not created. This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.
There is no log created, and even when I enable logging this error does not log.

A reboot solves it for 3-4 days, but it comes back every time. Once it hits, then any further communication is dead...and everything continues to fail until a reboot.

I am using 6.3.2 version WinSCP
There are no stale processes WinSCP in the Task Manager.

I am attaching the log file

Do you have any idea what could be causing this?
Thanks

I'm sorry, but I have no clue. How many sessions does it take for the problem to appear?

I cannot say for sure, it varies. Last time, the problem appeared 3-4 days after the server reboot, with approximately 200 sessions initiated daily

I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.

Hi,

I guess I have the same problem on Windows Server 2019 using WinSCP 6.5.5. Every couple of days, a few of our uploads fail with the error message: "WinSCP process terminated with exit code 3."
I usually works again the next time without a reboot being necessary.
I've attached a log file, I anonymized the SFTP server address in it.
Could you maybe send me the debug version?

Anonymous wrote:

Hi,

I guess I have the same problem on Windows Server 2019 using WinSCP 6.5.5. Every couple of days, a few of our uploads fail with the error message: "WinSCP process terminated with exit code 3."
I usually works again the next time without a reboot being necessary.
I've attached a log file, I anonymized the SFTP server address in it.
Could you maybe send me the debug version?

This was my post, seems like I wasn't logged in