Question

Getting Invalid REST comand trying to do a download, not sending REST command

Answer 1

This is bizarre. Is it possible that the file is being truncated on the server while you are downloading?

Have you tried using FIlezilla, and if so, was it successful?

Comments

Try the latest version, 2.2.3. It looks like it may be fixed in that version.

---

Okay, just downloaded and will try it.

---

It didn't help.  Here's the log from where the .NET ran (and I verified it was using the 2.2.3 version):

DEBUG [FTPConnection] 15 Sep 2015 14:04:37.612 : DownloadFile(C:\Projects\Badger Central\Source\Feature\0823\Factoring\Badger.Core.Services.Tests\bin\Debug\CCData091515020937.txt,CCDATA.TXT)
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.616 : ---> REST 0
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.663 : 350 Restarting at 0. Send STORE or RETRIEVE
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.667 : ---> PASV
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.718 : 227 Entering Passive Mode (206,212,89,52,34,199)
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.718 : Server supplied address=206.212.89.52
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.719 : Server supplied port=8903
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.719 : autoPassiveIPSubstitution=True
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.720 : remoteAddr=206.212.89.52
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.720 : Substituting server supplied IP (206.212.89.52) with remote host IP (206.212.89.52)
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.720 : NewPassiveDataSocket(206.212.89.52,8903)
INFO [BaseSocket] 15 Sep 2015 14:04:37.721 : Connecting to 206.212.89.52:8903 with timeout 120000 ms
DEBUG [BaseSocket] 15 Sep 2015 14:04:37.763 : Successfully connected to 206.212.89.52:8903
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.763 : Connected
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.764 : ---> RETR CCDATA.TXT
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.964 : 554 Invalid REST argument.
DEBUG [FTPControlSocket] 15 Sep 2015 14:04:37.964 : Expected reply codes = [125,150] (strict=False)
ERROR [FTPClient] 15 Sep 2015 14:04:37.965 : Caught exception Invalid REST argument. (code=554)
ERROR [FTPClient] 15 Sep 2015 14:04:37.966 : Caught exception
ERROR [FTPClient] 15 Sep 2015 14:04:37.966 : EnterpriseDT.Net.Ftp.FTPException: Invalid REST argument. (code=554)
ERROR [FTPClient] 15 Sep 2015 14:04:37.966 :    at EnterpriseDT.Net.Ftp.FTPControlSocket.ValidateReply(FTPReply reply, String[] expectedReplyCodes)
ERROR [FTPClient] 15 Sep 2015 14:04:37.966 :    at EnterpriseDT.Net.Ftp.FTPClient.InitGet(String remoteFile)
ERROR [FTPClient] 15 Sep 2015 14:04:37.966 :    at EnterpriseDT.Net.Ftp.FTPClient.GetBinary(String localPath, String remoteFile)
WARN [FTPConnection] 15 Sep 2015 14:04:37.973 : Could not get length of file 'C:\Projects\Badger Central\Source\Feature\0823\Factoring\Badger.Core.Services.Tests\bin\Debug\CCData091515020937.txt'
WARN [FTPConnection] 15 Sep 2015 14:04:37.973 : System.IO.FileNotFoundException: Could not find file 'C:\Projects\Badger Central\Source\Feature\0823\Factoring\Badger.Core.Services.Tests\bin\Debug\CCData091515020937.txt'.
WARN [FTPConnection] 15 Sep 2015 14:04:37.973 :    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
WARN [FTPConnection] 15 Sep 2015 14:04:37.973 :    at System.IO.FileInfo.get_Length()
WARN [FTPConnection] 15 Sep 2015 14:04:37.973 :    at EnterpriseDT.Net.Ftp.FTPConnection.GetLocalFileSize(String localPath, Boolean logExceptionAsWarn)

---

Ok, I'll take a look tomorrow - I'm pretty sure we've fixed this so it may not be out in edtFTPnet.

---

I've got a new build for you to try - please email support at enterprisedt dot com for a link.