hiteksoftware.com

[ajharn]

Hello,

I am using Automize 8.18. I have a working Commons FTP profile that I use with several tasks that both PUT and DELETE files. I am now trying to do a GET from the same site, and it invariably returns that there are no files to GET even though the remote directory is full of qualifying files.

I believe I have ruled out a permissions issue, because I can connect to the site from the connect button on the Automize FTP Profiles page and navigate to the correct folder and download the files successfully. I can also download files from this folder via other FTP clients.

The remote folder name is correct in the task because the CWD reports successful in the task log.

I have set the task up as basic as possible, by selecting the profile, selecting the remote and local folders and leaving filename blank to select all files. I have also tried Filename as a *. I have also setup a FTP Monitor task to check the remote folder. This task correctly returns the names of all the files in the remote folder. I have then used the Filenames variable from the Monitor task in the Get task. In every case, the GET task returns zeros for all values in the FTP Session summary.

If I change the task to a PUT task w/o changing any other options, the task correctly uploads files from the local to the remote folder.

If I use an FTP Commands task, connect to the site, CWD to the correct folder and do an MGET:: the task correctly downloads all files.

I simply cannot get the GET task to work, but I believe I have ruled out permissions and profile setup as causes here. Please let me know how to move forward in troubleshooting this issue.

Thanks.

[Robert]

If you are using 8.18, please try the FTP jscape task and see if you have the same issue. That will give us a clue if it is server or client side error.

[ajharn]

I tried it as an FTP-J and the task log reveals the following error for every file:
Failed to obtain file information object for: /Pending/Maan/Final/INV

Where the file name it is trying to get is INV, ONE.

So it is choking on the first space in every filename.

Unknown if this is the same problem the Commons FTP module is having. Please advise. Thanks.

[ajharn]

CORRECTION:

Above I said it was choking on the first space in every file...

It is actually choking on the first comma in the file name.

So yes, the files have commas and spaces like "LAST, FIRST"

Please advise. Thanks.

[Robert]

we could reproduce this issue. at this time we are unsure if this is a ftp protocol related issue with regards to , in the filename or something in the ftp task code.

we are looking into this and if it is some issue in the task code, then we will put the fix into the next patch update.

[ajharn]

Hi Guys,

I can't download the 8.19 patch. I get a zero length file when I download it. Can you please check on it.

I did see that patch notes show the comma in filename problem as resolved. Thanks much!

[Robert]

Thanks for the information. we have put up the correct file. It was a failed upload while publishing. all other 8.19 files seem ok.