bug in PutFile

Question

it hangs when I call PutFile SOMETIMES.
I don't know why. and if I set the TimeOut to 5 then it throw a following exception.

ERROR [UploaderControls.UploadingStatusForm] 10 9 2005 08:57:10.853 : Transfer Error: Unable to read data from the transport connection.
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.StreamReader.ReadBuffer()
at System.IO.StreamReader.ReadLine()
at EnterpriseDT.Net.Ftp.FTPControlSocket.ReadReply()
at EnterpriseDT.Net.Ftp.FTPClient.ValidateTransfer()
at EnterpriseDT.Net.Ftp.FTPClient.Put(String localPath, String remoteFile, Boolean append)
at EnterpriseDT.Net.Ftp.FTPClient.Put(String localPath, String remoteFile)
at UploaderControls.UploadingStatusForm.startUploading() in f:\works\test\main\uploadercontrols\uploadingstatusform.cs:line 675

Answer 1

I had this problem too, do not know why.

Answer 2

I had this problem too, do not know why.

I got this problem too. I happened to find that, for certain files, if we use 'binary' to putfile, it will hang for ever, no error message. if we change to 'ascii', then it solved this problem. but sometimes, for some other files, 'ascii' does not work while 'binary' works.

any1 had this problem too?

Answer 3

You've set the timeout to 5 millseconds. Set it to 5000.

it hangs when I call PutFile SOMETIMES.
I don't know why. and if I set the TimeOut to 5 then it throw a following exception.

Answer 4

I had this problem too, do not know why.

I got this problem too. I happened to find that, for certain files, if we use 'binary' to putfile, it will hang for ever, no error message. if we change to 'ascii', then it solved this problem. but sometimes, for some other files, 'ascii' does not work while 'binary' works.

any1 had this problem too?

I have had this problem too, but with Get().