Have you tried using PASV mode instead of PORT? The "550" response is questionable, I'm not why you received that w/o an error message.
Yes I have tried PASV and get a different error 425 Can't open data connection. Is this associated to my local PC or the server I'm trying to access?
 Thu 29May14 12:58:59 - 227 Entering Passive Mode (10,202,38,61,224,99)
 Thu 29May14 12:58:59 - Private IP address returned by the server in response to PASV command.
 Thu 29May14 12:58:59 - Converting private IP address 10.202.38.61 to public IP address 220.127.116.11.
 Thu 29May14 12:58:59 - Opening passive mode data connection to 18.104.22.168, port 57443.
 Thu 29May14 12:59:20 - Data connection failed using Passive Mode (PASV), automatically retrying using Active Mode (PORT).
 Thu 29May14 12:59:20 - PORT 47,23,21,53,204,67
 Thu 29May14 12:59:20 - 200 Port command successful
 Thu 29May14 12:59:20 - MLSD
 Thu 29May14 12:59:20 - 150 Opening data channel for directory list.
 Thu 29May14 12:59:30 - 425 Can't open data connection.
 Thu 29May14 12:59:30 - (Action: "C:\Upload" to "/") - Action failed (Last Error Message: ).
 Thu 29May14 12:59:30 - (Task: fd 33) - Execution failed (Last Error Message: ).
 Thu 29May14 12:59:30 - (Task: fd 33) - Next scheduled execution on Thursday, May 29, 2014 13:08:14
 Thu 29May14 12:59:33 - QUIT
 Thu 29May14 12:59:33 - 221 Goodbye
PASV mode requires the server's router/firewall to allow certain ports through. If they don't then that might explain why you receive the:
425 Can't open data connection.
PORT looks like it establishes the data connection, but the error that's returned after the LIST command is weird. The RFC (/Net/dxcern/userd/timbl/hypertext/WWW/Protocols/rfc959.txt) states:
550 Requested action not taken.
File unavailable (e.g., file not found, no access).
My hunch is that is a permissions issue (i.e., your user doesn't have access to that folder). Can you verify that the user you use in Scheduler is the same as the one in FTP Voyager, since you're manual tests confirmed that when using FTP Voyager everything works? Another test is to perform the synchronize action using FTP Voyager (instead of scheduler) just to compare results.