Hello all,
I'm stumped with the following problem: I need to use a command line to upload a file at the same time every day. Here is my command line:
coreftp.exe -site Nationwide -u C:\DataFeeds\StandardFeeds\Data\OAMCOMB\Payments_FC7_20090306173059.csv -p /
This upload fails with the following error:
STOR .Payments_FC7_20090316173217.csv
Cannot send/receive/list at this time, connection busyPayments_FC7_20090316173217.csv - 0 bytes transferred
However, if I manually launch CoreFTP, connect to the very same site I use in the command line, then click and drag the file in question, the file uploads just fine.
I've done my best to eliminate any errors I might be making and I've had no luck. This problem started when I started executing the command line on a new computer (the old one went back on lease). I'm not sure what else to try to identify/fix this problem. Any ideas?
TIA,
Kate
Upload using command line fails while manual works fine
Thanks for replying! I tried the command line again this time using corecmd.exe and got the same results.
I should also mention that periodically, rather than getting the cannot send/receive/list at this time error, I get:
Server returned invalid response to FXP_READ
I don't know if that helps.
Thanks,
Kate
I should also mention that periodically, rather than getting the cannot send/receive/list at this time error, I get:
Server returned invalid response to FXP_READ
I don't know if that helps.
Thanks,
Kate
Actually, I think it might be fixed. I tried the command line:
corecmd.exe sftp://username:password@site/path/ –ssh -u c:\local_path\filename.ext
suggested by this thread:
http://www.coreftp.com/forums/viewtopic.php?t=55174
...and that worked.
I'm glad it worked, but I can't figure out why. The command line sends the exact same information that's saved in the session...
I'll keep an eye on my scripts tomorrow to confirm this fix works.
Thanks,
Kate
corecmd.exe sftp://username:password@site/path/ –ssh -u c:\local_path\filename.ext
suggested by this thread:
http://www.coreftp.com/forums/viewtopic.php?t=55174
...and that worked.
I'm glad it worked, but I can't figure out why. The command line sends the exact same information that's saved in the session...
I'll keep an eye on my scripts tomorrow to confirm this fix works.
Thanks,
Kate