.NET library – error while running scheduled task

WinSCP process terminated with exit code 3 and output "", without creating a log file.

WinSCP process terminated with exit code 3 and output "", without creating a log file.

WinSCP.SessionLocalException: WinSCP process terminated with exit code 3 and output "", without creating a log file.

[2013-06-09 15:10:26.972Z] [0001] Exception: WinSCP.SessionLocalException: WinSCP process terminated with exit code 3 and output "", without creating a log file.
[2013-06-09 15:10:26.972Z] [0001] Exception: WinSCP.SessionLocalException: WinSCP process terminated with exit code 3 and output "", without creating a log file.
at WinSCP.Session.Open(SessionOptions sessionOptions)

My error is "WinSCP.SessionRemoteException: Connection failed."

Exception calling "Open" with "1" argument(s): "WinSCP process terminated with exit code 3 and output "", without creating a log file."

[Reflection.Assembly]::LoadFrom("C:\OpalisOneSource\Logs\fldOptiCash\WinSCP-5.1.5\WinSCP.dll") | Out-Null
 
$sessionOptions = New-Object WinSCP.SessionOptions
$sessionOptions.Protocol = [WinSCP.Protocol]::Sftp
$sessionOptions.HostName = "172.19.1.81"
$sessionOptions.UserName = "opalis"
$sessionOptions.Password = "PASSWORD CHANGED HERE"
$sessionOptions.SshHostKeyFingerprint = "ssh-rsa 2048 RSA-KEY-CHANGED-HERE"
 
$session = New-Object WinSCP.Session
$session.Open($sessionOptions)
 
$transferOptions = New-Object WinSCP.TransferOptions
$transferOptions.TransferMode = [WinSCP.TransferMode]::Binary
$transferOptions.FilePermissions = $null
$transferOptions.PreserveTimeStamp = $false
 
$localpath = "C:\OpalisOneSource\Logs\fldOptiCash\FOLDER HERE"
$remotepath = "/FOLDERA/FOLDERB/*.csv"
 
$transferResult = $session.GetFiles($remotepath, $localpath, $False, $transferOptions)
 
$arr = New-Object collections.arraylist
$transferResult.transfers | foreach{$arr.Add($_.FileName)}
 
$session.Dispose()

• Seeing this for a while now, apparently since Feb-Mar. Using Visual Cron to kick off the task, running ~ 20 times/ hour (20 separate jobs, each runs every hour, staggered)
  
• Visual Cron runs a Perl script that kicks off a filemasked download(this was happening on another server with uploads as well but has been replaced with a different batch job).
  
• Last reboot fixed the problem for ~ 2 weeks. This system is crucial to several environments, and can't be rebooted without announced downtime, so the problem is a bit exacerbated.
  
• Short sessions, usually 4-8 files ranging from 1-4000 MB in size.
  
• Once the bug hits, WinSCP will not run from *any* automated process until the system is rebooted. It will not run a simple command line connect from windows task scheduler, from the automation software we are using, or anywhere else automated, regardless of user account.
  
• The process that launches it (Visual Cron)runs as a service, but restarting the service has no effect.
  
• Userland command Windows continue to function normally.
  

Could not open session, WinSCP process terminated with exit code 3 and output "", without creating a log file.

error code 3. No log file is created.

jasongk wrote:

I too have this error. When do you think this error could be fixed?
(please don't take this as i'm pressuring you or anything to fix this, i'm just curious)

MEMScadman wrote:

This problem is not limited to .NET library use. I am having a similar issue executing a WinSCP.com 5.2.1 script from a batch script inside a service built on srvany. The OS is Windows Server 2008 R2 Standard SP1.

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.

JKL wrote:

I have already tried versions 5.1.7 and 5.2.6.

Compatibility mode makes no difference.

Can you help?

While the fixed versions no longer gradually exhaust system resources, they cannot recover resources exhausted by previous buggy versions. So it's still necessary to restart affected machine to recover the system.

martin wrote:

Did you restart your machine?

While the fixed versions no longer gradually exhaust system resources, they cannot recover resources exhausted by previous buggy versions. So it's still necessary to restart affected machine to recover the system.

Army wrote:

Basically, every time the error code appears in the Task Scheduler it's for sure that there's an update requiring restart in the background.
I'm not entirely sure if it's connected to the atoms mentioned in the StackOverflow thread, but it's very annoying and would appreciate any solutions you might have.

martin wrote:

Is the 0xc0000142 an actual exit code of WinSCP? Can you give us more details on the task? (how does it interact with WinSCP)

winscp process terminated with exit code 3 and output....

WinSCP process terminated with exit code 3.
There was no output. Response log file C:\Windows\TEMP\wscp4310.03C09FDF.tmp was not created.
This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.