Post a reply :: Support Forum

martin

Re: Console Script Report No Error Yet .NET Apps Do Report Error

2009-08-02

UpsideDownTire wrote:

How does one determine the specific cause for a failure when the ExitCode is one? The only resource is to visually examine the log?

Log file contains only errors specific to session. You may have some script level error as well, such as unrecognised command. Such error can be seen in the output only (processWinSCP.StandardOutput.ReadToEnd). Post the output if you need a help.

UpsideDownTire

Re: Console Script Report No Error Yet .NET Apps Do Report Error

2009-07-31 17:44

I am very aware of that reference.

My application decides that an error has happened through the use of your examples from your guide here.

Here's a snip of my code:

Dim processWinSCP As Process = New Process()
 
Dim logname As String
 
logname = "C:\log.txt"
 
' Build the Process
processWinSCP.StartInfo.FileName = "C:\Program Files\WinSCP\WinSCP.com"
processWinSCP.StartInfo.Arguments = "/log=" + logname
processWinSCP.StartInfo.UseShellExecute = False
processWinSCP.StartInfo.RedirectStandardInput = True
processWinSCP.StartInfo.RedirectStandardOutput = True
processWinSCP.StartInfo.CreateNoWindow = True
processWinSCP.Start()
 
' Feed in the scripting commands
processWinSCP.StandardInput.WriteLine("option batch abort")
processWinSCP.StandardInput.WriteLine("option confirm off")
processWinSCP.StandardInput.WriteLine("open sftp://userName:passWord@ftp-site.com:22 -hostkey=""ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx"" -timeout=180 ")
processWinSCP.StandardInput.WriteLine("cd /datafiles")
processWinSCP.StandardInput.WriteLine("option transfer binary")
processWinSCP.StandardInput.WriteLine("get -preservetime BigMotherOfAnXMLFile.xml C:\BigMotherOfAnXMLFile.xml ")
processWinSCP.StandardInput.WriteLine("close")
 
' Collect all output (not used in this example)
Dim output As String = processWinSCP.StandardOutput.ReadToEnd()
 
Debug.Print(output)
 
' Wait until WinSCP finishes
processWinSCP.WaitForExit()
 
 
' Success (0) or error?
If processWinSCP.ExitCode <> 0 Then
 
        Console.WriteLine("Error occured")
 
End If

How does one determine the specific cause for a failure when the ExitCode is one? The only resource is to visually examine the log?

martin

Re: Console Script Report No Error Yet .NET Apps Do Report Error

2009-07-31

UpsideDownTire wrote:

My problem is my applications are telling me an error happened.

How does your application decide that error happens?

In all logs, from apps and console, I see a line with "Status/error code: 1". I am assuming that means an error happened. Is this a correct assumption, an error did occurr? If so, how do I find out the error?

That's wrong assumption.

Please read FAQ. If that does not help, come back.

UpsideDownTire

Console Script Report No Error Yet .NET Apps Do Report Error

2009-07-29 23:58

My problem is my applications are telling me an error happened. The console execution of the original script does not report an error. So I am very confused as to whom to believe. In every case, my downloaded test file is just fine. It more than 7 MB in size.

I first tested the script in console then copied it to VS 2008 in both VB.NET and C#.

The script and the .NET applications are based upon your samples in the .NET Guide. Both apps suggest the exit code is one (an error ocurred). The script run in console does not report an error.

In all logs, from apps and console, I see a line with "Status/error code: 1". I am assuming that means an error happened. Is this a correct assumption, an error did occurr? If so, how do I find out the error?

WinSCP

Workstation OS

Here's my script:

Here's my log from Windows 2003 Server: