Ok, so what I am trying to establish is that it must be my software that is causing the problem. There must be some sneaky situation where I am triggering a new command before the previous one has finished.
So there is definitely no way it is either the FTP client component itself or some network problem that could produce this? Regards Graham -----Original Message----- From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of Angus Robertson - Magenta Systems Ltd Sent: 10 June 2013 09:43 To: twsocket@lists.elists.org Subject: Re: [twsocket] FTP component not ready > As far as I know, using the Async commands, the "FTP component not > ready" error occurs if you initiate a command before the previous one > has generated the RequestDone event. Yes, the State variable is checked to ensure the next command can be performed safely. > I have one customer who is getting this error about once a week, so > the question is: Can this error be produced by something else. A > network error or some strange issue in the server maybe? State can change at any time while a command is being executed and sometimes two or more commands are executed in sequence. State changes to ftpNotConnected when the control channel disconnects, which will cause the not ready error when the next command is executed. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
