> The original problem is that the "FTP component not ready" just
> turns up very occasionally from doing a series of getAsync commands.
> So assuming that the error might be from a PORT or PASV, should the
> sequence of events I take be to call ftp.Abort followed by some
> sort of restart of my
> I ran into a similar problem while testing some of my software.
> After a couple of days of pulling my hair out, I thought to change
> out my router and the problem disappeared. I never did determine
> what was wrong with the router.
Many routers support NAT, which is quite messy for the FTP
ubject: Re: [twsocket] FTP component not ready
Ok, so what I am trying to establish is that it must be my software
that is causing the problem.
I didn't say that, it's probably the control channel dropping, either a
network problem or the server disconnecting the session.
There
rg
Subject: Re: [twsocket] FTP component not ready
> Ok, so what I am trying to establish is that it must be my software
> that is causing the problem.
I didn't say that, it's probably the control channel dropping, either a
network problem or the server disconnecting the sessi
> Ok, so what I am trying to establish is that it must be my software
> that is causing the problem.
I didn't say that, it's probably the control channel dropping, either a
network problem or the server disconnecting the session.
> There must be some sneaky situation where I am
> triggering a n
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
> 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
