This application was written 18 months ago and has been running on-site
ever since, so it is very likely it is running the ICS release that
contained the Abort fault.
I'll try recompiling the sources with the latest ICS release and see how
that goes.
Thanks,
Dave
Arno Garrels wrote:
>David
David Lewis wrote:
> What is the 'right' way to close the connection down in such a way that
> the next attempt will be a 'clean' one? I presume I haven't closed
> everything down properly which is causing be to fail on the next
> connection.
Usually calling Abort aborts a dns lookup as well (whi
The error that appears in my log is:
ERR No Data (Winsock error #11004)
The log is generated by the first routine ("if(Error)"), I presume when
a command has caused an error due to the network being interrupted.
I would presume that the second routine (the unknown RqType) doesn't
fire at all a
Hello David,
Do you have logs indicating which one cause the break, and what error /
RqType it is ?
I think in both cases you should call Abort();
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Monday, November 14, 2005, 10:33, David Lewis
I've got an application that I wrote a while ago now that is starting to
have some issues I need to look into.
Basically, this application contains a process that regularly polls for
emails (every 5 minutes) and gathers any available, stripping off up to
60 jpg attachements and processes them.
