Topic "WinSCP process terminated with exit code 3 and output """

Author Message
Shyronosov Alex

Guest


Hello Everyone,
Our .NET application uses WinSCP software to work with SFTP servers. It's running on different machines, however 1 week ago 2 of them started to fail with the following exception:

WinSCP.SessionLocalException, WinSCP process terminated with exit code 3 and output "", without responding (response log file D:\local\Temp\wscp1028.00ADA812.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)

This error doesn't occur always, but after some period of time. Once error occurs it fails always until we restart the entire application. After application restart it successfully works 10-20 hours and approx. 15K-30K succeeded requests. Then the error starts again.

We have already upgraded to the last version of WinSCP (5.7.7), however the issue still takes place. What could be the root cause and what steps could be done to fix the issue? Any help is appreciated.

Thanks, Alex
Advertisements
Yannick

Guest


Hi,

we have the same issue on our production servers since 3/7/2016.

Our .Net application using the Winscp .NET wrapper is a windows service that runs under a specific build-in account. When I run the application from the console (with my user account) everything works fine. If a put my user on the windows server (instead of the build-in account) I receive the same error.

We are using Windows Server 2008R2 enterprise and the latest version of WinScp. Since rebooting the production machine is not an option, I hope someone could give us some advice to fix this issue?

Thanks,
Yannick
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24995
Location: Prague, Czechia
Sorry for late answer. It took me while to find a time to test this. Though I was able to open 100K sessions over a span on about 24 hours in a single application run without any problem.

Can you try to use the Process Monitor to debug the failing start of winscp.exe?

Your duplicate question on Stack Overflew: http://stackoverflow.com/q/38170507/850848
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24995
Location: Prague, Czechia
Yannick wrote:
Our .Net application using the Winscp .NET wrapper is a windows service that runs under a specific build-in account. When I run the application from the console (with my user account) everything works fine. If a put my user on the windows server (instead of the build-in account) I receive the same error.

We are using Windows Server 2008R2 enterprise and the latest version of WinScp. Since rebooting the production machine is not an option, I hope someone could give us some advice to fix this issue?

What version of WinSCP are you using? How exactly are you using the .NET assembly? This does not look like the same problem actually.
Guest




martin wrote:
Yannick wrote:
Our .Net application using the Winscp .NET wrapper is a windows service that runs under a specific build-in account. When I run the application from the console (with my user account) everything works fine. If a put my user on the windows server (instead of the build-in account) I receive the same error.

We are using Windows Server 2008R2 enterprise and the latest version of WinScp. Since rebooting the production machine is not an option, I hope someone could give us some advice to fix this issue?

What version of WinSCP are you using? How exactly are you using the .NET assembly? This does not look like the same problem actually.


We are using version 5.7.7 and we use the library in a windows service (under the Local System account) on a Windows Server 2008 R2 virtual machine. We have multiple windows services registered and running on the same machine, and they all throw the same error. However, when I run the service from the command line (console) it works fine.

The issue was solved when we rebooted the virtual machine during our maintenance window, but of course we need some kind of solution for this because we can't reboot the machine at any time we want to.

Hope you can help,
Yannick
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24995
Location: Prague, Czechia
Were you always using 5.7.7? Or did you use older version before?
Yannick

Guest


martin wrote:
Were you always using 5.7.7? Or did you use older version before?


We started with version 5.7.7, we did not use any older version before.
Yannick

Guest


Yannick wrote:
martin wrote:
Were you always using 5.7.7? Or did you use older version before?


We started with version 5.7.7, we did not use any older version before.


I must correct my answer, we do use an old COM WinScp interface (file WinSCP.com of 18/07/203). We call this COM from a .NET executable with the help of the Process class. The .NET application itself runs in a Windows Task with a dedicated build-in user account.

I just discovered that this process was also failing like the other once, but I could not find any information of which process (Window Task or Windows Service(s)) did trigger the failure.

Is this is known issue on older versions? Maybe we need to upgrade the old WinScp.com file...

Kind Regards,
Yannick
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24995
Location: Prague, Czechia
Yes, it's a know issue with WinSCP .NET assembly 5.2.4 and older:
https://winscp.net/tracker/show_bug.cgi?id=996

And as commented in the tracker:
Quote:
While the fixed versions no longer gradually exhaust system resources, they cannot recover resources exhausted by previous buggy versions.


So the old version breaks even the application that uses the new version.
Yannick

Guest


Thank you for the information. We'll upgrade the old clients to the new version and hope it won't break again Wink

Kind Regards,
Yannick
Advertisements

You can post new topics in this forum






Search Site

What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!

Donate

About donations

$9   $19   $49   $99

About donations

Recommend

WinSCP Privacy Policy

WinSCP License