Ask a Question

Invalid FTP response (B0)?

0 votes
by (120 points)

Hello,
I'm working with Rebex.Net.Ftp version 4.0.5085.0
Sometimes i getting following error while uploading the:

Invalid FTP response (B0). + Stack Trace => at Rebex.Net.IJ.DC(Int32 A)
at Rebex.Net.Ftp.PL(Int32 A, Boolean B)
at Rebex.Net.Ftp.PL(Int32 A)
at Rebex.Net.Ftp.AM(String A, Boolean B, VJ C, AH D, Int64 E, FtpTransferState H)
at Rebex.Net.Ftp.VN(String A, String B, Stream C, Int64 D, Int64 E, AH H)
at Rebex.Net.Ftp.VN(String A, String B, String C, Int64 D, Int64 E, Int64 H, AH I)
at Rebex.Net.HJ.FC(UG A, UG B, String C, String D, Int64 E, Int64 H)
at Rebex.Net.HJ.FC(UG A, UG B, String C, String D, Boolean E)
at Rebex.XG.JE(String A, String B, UG C, UG D, UG E, UG H, Boolean I, Boolean J, Boolean L)
at Rebex.XG.IE(VG A)
at Rebex.XG.FE()
at Rebex.XG.AE(TransferAction A, TG B, String C, TransferMethod D, MoveMode E, LinkProcessingMode H, ActionOnExistingFiles I, UG J)
at Rebex.Net.Ftp.HO(SG A, String B, TransferMethod C, MoveMode D, LinkProcessingMode E, ActionOnExistingFiles H)
at Rebex.Net.Ftp.GO(String A, String B, TraversalMode C, TransferMethod D, MoveMode E, LinkProcessingMode H, ActionOnExistingFiles I, Boolean J)
at Rebex.Net.Ftp.Upload(String localPath, String remoteDirectoryPath, TraversalMode traversalMode, TransferMethod transferMethod, ActionOnExistingFiles existingFileMode)

Any ideas?
Thanks for assistance...

Applies to: Rebex FTP/SSL

1 Answer

0 votes
by (72.7k points)
edited by

Hello, it seems that the server really sent an invalid response (empty line).

Can you please send us Verbose communication log to support@rebex.net, so we can see more information about server responses?

It can be done like this:

// create new FTP client and initialize LogWriter
Ftp client = new Ftp();
client.LogWriter = new Rebex.FileLogWriter(
    @"C:\Logs\ftp.log", Rebex.LogLevel.Debug);

// connect, login and other stuff...
client.Connect();
client.Login();

// enable Verbose log for Upload
client.LogWriter.Level = LogLevel.Verbose;
client.Upload();
client.LogWriter.Level = LogLevel.Debug;

And my second question: what does it mean sometimes? Do you have some data which triggers the error always or does it fail randomly or does it fail always after 5 minutes of working?

...