RoboTask forum

I get the following message:
E: 9/11/2007 5:38:04 PM: FtpGetFile('/home/test/data/20050127/TEST.OUT') fails with message: 200 Switching to Binary mode.<CR><LF>227 Entering Passive Mode (XXX,XXX,XXX,XXX,XXX,XX)<CR><LF>550 Could not get file size.<CR><LF>550 Failed to open file.<CR><LF>

First of all, I don't understand the IP address that's listed as XXX,XXX,XXX,XXX,XXX,XX  - I obviously replace the actual numbers with "X", but why are there 6 sets of numbers and why are the separated by commas? 
Assuming this is irrelevant to fixing the problem, what is wrong, and if it's a configuration on the Linux server, any ideas as to what I should check?
Thanks
 
 

Hmm... Robotask uses WININET engine (built-in system engine) for FTP operations.
I think that this has happened because of some settings of FTP. We tested this on Windows and Linux FTP. Synchronization worked fine.

Are you sure that you have enough rights to write or delete files in FTP in this directory?

Try to turn on passive mode in "FTP Login" action. It is turned off by default.

I have tried ftp'ing using the command prompt in windows and everything works fine, so it's not the server and it's not the workstation.
here is the output from my manual ftp results:
ftp> get rsx.out
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for rsx.out (20816 bytes).
226 File send OK.
ftp: 20816 bytes received in 0.00Seconds 20816000.00Kbytes/sec.
ftp> lcd
Local directory now C:\Documents and Settings\NS.
ftp>
I also change my Robotask job to "Passive" on the logon and that didn't help.
Any other recommendations?

I've tested again on our Linux FTP, this is working fine.
I think that this relates to access rights to files. Maybe files was created by another user or something similar.

Can you create test account on your FTP for me, in order I could simulate your situation?
Mail me to my address oleg(at)robotask.com

Was there ever a resolution to this issue? I'm encountering the same issue with my FTP synchronization.

I'm sure that this problem relate to secure settings of your FTP. Unfortunately we can't simulate this situation on our servers.

I'm having the same issue with FTP synchronization. Looks like this problem was never reproduced and resolved. I can help you with reproducing this issue if Robotask team is interested in fixing this.Thanks,Mansoor