But you know precisely which operation failed. FTPGetFile made a successful connection, attempted to get the file, failed, closed connection, and again you know the exact file name. Try downloading the same file using standard command line FTP utility. Make sure the file you are trying to download exists and it is not a directory and it is not a link to some other file. Also check that you don't have "special ASCII characters" in both the source and destination file names, like "c:\temp\xxx.txt" will be be converted to "c:[tab]emp\xxx.txt." If this is the case, use double-backslashes. : When this job originally ran, I was in debug mode and I had trace enabled. : The trace window shows a successful login, a couple of blank lines, and : then a "Connection closed" message. No information is displayed : about the error other than the 24x7 dialog box I previously described. : That's why I was wondering if there was anything else (like a log that showed : what native FTP commands were created by the FTPGetFile statement) that I : could use to determine what the host doesn't like. Without knowing what : happens "behind the scenes" when FTPGetFile executes, it will be : difficult to diagnose this problem. But, if I could recreate the FTP Get : manually from the command line, I may be able to figure it out. : Thanks.
|