WinSCP process terminated with exit code 3

Advertisement

RICH_III
Joined:
Posts:
3

WinSCP process terminated with exit code 3

We've been using WinSCP through a .NET connector in Dynamics NAV BC for a few years now for automated processes but a few weeks ago I started receiving this error below. I found some older messages on this in the Bug 996 tracker thread and tried upgrading to the latest version but it did not help. Restarting our server corrects it for a few days but it always seems to return.

I've attached the debug log.

Error Message:
Exception: WinSCP.SessionLocalException: WinSCP process terminated with exit code 3. There was no output. Response log file C:\Users\{username}\AppData\Local\Temp\wscp235C.01A8D5D7.tmp was not created. This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.
at WinSCP.Session.Open(SessionOptions sessionOptions)
  • winscpdebug.log (9.18 KB, Private file)

Reply with quote

Advertisement

Advertisement

Krishanu
Guest

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

Hello Ritchi,

Did upgrading to WinSCP 5.21 helped?

Thanks, Krishanu

Reply with quote

ValentinT
Guest

Same error on version 5.21.6

Hello There,

I have the same error on version 5.21.6
WinSCP.SessionLocalException: WinSCP process terminated with exit code 3. There was no output. Response log file C:\Users\SVC_SCONSOLE\AppData\Local\Temp\wscp0FC0.02C8B46A.tmp was not created. This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.
à WinSCP.Session.Open(SessionOptions sessionOptions)
WinSCP works normaly during several hours and, suddently i dont know why it stop working. Restarting my app permit to re work normally for several hours and the problem occurs again..
My app is opening two new sftp sessions every 5 minutes (and close and dispose them after usage)

Reply with quote

Advertisement

martin
Site Admin
martin avatar

Re: Same error on version 5.21.6

@ValentinT: Please post debug file from the last session that works (and its session log) and the first session that does not. Also, did you check memory consumption (overal and of your application), when it stops working? Isn't there some leak? Did you check running processes, if there are some pending winscp.exe processes?

Reply with quote

Advertisement

You can post new topics in this forum