• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 424
  • Last Modified:

Why only getting partial StandardOutput of a "Process.Started" FTP called from VB.NET?

I have a VB.NET application that does an FTP and redirects the Standard Output to a file.  I only get partial data from the StandardOutput. The missing contents are the actual FTP replies (like "150 Open...." and "226 Transfer.....").
I've scoured this site and the internet, and have seen several others ask this similar question but none have any answers.

All is well is most situations, except of course in the one environment where the code will run in Production! I perform this FTP Routine two times in my code, sending output files to two different mainframe IPs. In my Dev environment (which happens to be XP), all is hunky-dorey for both routines; I get my desired reply codes.  In my Test environment (which happens to be 2003), all is hunkey-dorey for one routine - the other in-house mainframe box does not produce the reply codes in the piped output log. However, when I do an FTP from the command prompt (in both Dev and Test environs), the Reply Codes are indeed there.

What's the .NET mystery? I suspect it's .NET and not the mainframe since all other combos work just fine.

Here's a code snippet:

FTPLabel:
            Dim FixedLiteral As String = FileParam4
            Dim DOS As New Process
            Dim pinfo As New ProcessStartInfo("ftp.exe")
            pinfo.Arguments = "-n -d -s:"
            pinfo.Arguments += FixedLiteral
            pinfo.RedirectStandardOutput = True    ' set to "true" to enable logging
            pinfo.RedirectStandardError = False
            pinfo.UseShellExecute = False     ' set to true to make silent/background

            ' Execute the process
            DOS = Process.Start(pinfo)
            If DOS.Start() Then
                ' Create the file for storing the output of the process
                Dim outfile As New System.IO.StreamWriter(FileParam5)
                outfile.Write(DOS.StandardOutput.ReadToEnd)
                ' Make sure the process has completed
                DOS.WaitForExit()
                ' Dump all the output from the process into the file
                'outfile.Write(DOS.StandardOutput.ReadToEnd)   'original line and location
                'outfile.WriteLine(DOS.StandardOutput.ReadToEnd)
                outfile.Close()
            End If
            'After the FTP process is done, I must open up the log file and check for the string "226 File received ok". If I don't find it, then I will have to try the FTP again.
            mySRftp = New StreamReader(FileParam5)
            mySRText = mySRftp.ReadToEnd()
            If InStr(mySRText, "226 Transfer completed") > 0 Then
                'Remove the concatenated ftp'ed file.
                File.Delete(Localtitle)
            Else
                BadAttemptCnt += 1
                If BadAttemptCnt < 4 Then
                    SendFTPEmail(Localtitle, BadAttemptCnt)
                    mySRftp.Close()
                    GoTo FTpLabel
                End If
            End If

This is the Output that is produced in DEV, that I want to see on the TEST box:

ftp> Connected to 162.xxx.xxx.x.
open 162.xxx.xxx.x
220 Upstanding Systems FTP Server version 70.144.48 ready.
ftp> ---> user XXXXXX
USER XXXXXX
331 User name is okay; need password.
--->
PASS XXXXXXXX
230 User logged in, proceed.
ftp> ftp>
---> ascii
TYPE A
200 Representation Type is ASCII Non-print.
ftp> ---> quote SITE RECL 770
SITE RECL 770
200 recordLen is 770 Characters.
ftp> ---> put C:\inetpub\wwwroot\Joseph\OutgoingFdleMerge770\ConcatFile.txt 00000552
PORT 162,xxx,xxx,xxx,13,155
200 PORT command successful.
---> STOR 00000552
150 Opening data connection for 00000552 (162.xxx.xxx.xxx,3483).
226 Transfer completed to 00000552 ON PROGRAMMING.
ftp: 4632 bytes sent in 0.00Seconds 4632000.00Kbytes/sec.

ftp> ---> quit
QUIT
221 Goodbye.

This is the problematic output that I see on the TEST box:

---> open 162.xxx.xxx.x
user XXXXXX
USER XXXXXX
--->
PASS XXXXXXX
--->
ascii
TYPE A
---> quote SITE RECL 770
SITE RECL 770
---> put D:\Inetpub\wwwroot\Joseph\OutgoingFdleMerge770\ConcatFile.txt 00000554
PORT 162,xxx,xx,xx,5,29
---> STOR 00000554
---> quit
QUIT


0
bigsplash
Asked:
bigsplash
  • 3
  • 3
4 Solutions
 
bigsplashAuthor Commented:
P.S.   I tried the debug switch, as such  ---- pinfo.Arguments = "-n -d -s:" ----  since somebody else on another forum seemed to have success with this option. In or out, it doesn't work for me.

Also, I failed to mention that the FTP "Put" command itself is performing sucessfully.
0
 
gregoryyoungCommented:
               outfile.Write(DOS.StandardOutput.ReadToEnd)
                ' Make sure the process has completed
                DOS.WaitForExit()

this is definately backwards.
0
 
bigsplashAuthor Commented:
Yes, I thought so myself..... I just happened to see it written out that way on some site and tried it..... I've changed it back, yet no luck.
If DOS.Start() Then
                ' Create the file for storing the output of the process
                Dim outfile As New System.IO.StreamWriter(FileParam5)
                ' Make sure the process has completed
                DOS.WaitForExit()
                ' Dump all the output from the process into the file
                outfile.Write(DOS.StandardOutput.ReadToEnd)   'original line and location
                outfile.Close()
            End If
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
Bob LearnedCommented:
Is there any Unicode in the string?  You can write unicode:

Dim outfile As New System.IO.StreamWriter(FileParam5, System.Text.Encoding.Unicode)

Bob
0
 
gregoryyoungCommented:
could the status be being written to standard error instead of standard out ? just a thought.
0
 
bigsplashAuthor Commented:
No additional data is written when Unicode is specified.  :-(

Interesting thought about the StandardError.  I created and wrote to this file too, and nope - it's blank.

A friend just e-mailed this link to me http://www.dotnet247.com/247reference/a.aspx?u=http://support.microsoft.com/
default.aspx?scid=kb;EN-US;832679.   It's apparently a way to use ftp managed .NET code. Long article..... I may try this tomorrow.
0
 
gregoryyoungCommented:
there are quite a few managed ftp libraries

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now