October 9, 2009 at 11:24 am
Thanks! I'll give it a shot...
October 13, 2009 at 8:36 am
Ok, onto the next hurtle!
It's requiring something in the "remote path" parameter and it has to start with "/". In most cases, the remote path is governed by the account that's used to login. I typically do not specify a remote path. In some cases I'm transferring files to/from a VMS system, and that OS doesn't utilize /'s in the directory paths.
Any idears?
Thanks...
March 16, 2011 at 8:06 am
satish.t (10/9/2009)
The format is below"Server IP: Port.loginAccount.loginPWD"
EX: "192.168.1.1:21"+ @[user::FtpAcct]+"."+ @[user::FtpPwd]
192.162.1.1:21.Username.password
This worked for me... 🙂
All the best
The expression "192.168.1.1:21"+ @[user::FtpAcct]+"."+ @[user::FtpPwd] does not give a connection string in the format listed in the example below as there is no logic in the expression to place the "." after the port and before the loginAccount. Should the expression be:
EX: "192.168.1.1:21"+ "." + @[user::FtpAcct]+"."+ @[user::FtpPwd]
or am I missing something?
May 11, 2011 at 12:48 pm
Would you place this
"192.168.1.1:21"+ "." + @[user::FtpAcct]+"."+ @[user::FtpPwd]
in the ftp connection manager expressions for connection string?
Thanks
Colin
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply