Helo,
I try to use SmtpCli->CtrlSocket->CloseDelayed instead SmtpCli->Abort().
It's works much much better ! No more 10004 errors after cancelling timed
out
connections !
---
With best regards, Max Terentiev.
Business Software Products.
AMS Development Team.
[EMAIL PROTECTED]
- Original M
> This is the same line I have. The problem is that same code is all
> over the place in the source. Is there another version of the source
> without those debug statements or with conditional compilation
> directives?
There isn't but you can easily replace OutputDebugString by
//OutputDebugStrin
I disabled range checking in the .INC file and rebuilt the package and
it appears to be working for now.
The conditional compilation for debug code will be welcomed.
It seems to be an issue with Windows 98 machines from what I have seen.
Thanks guys.
-Johnnie Norsworthy
--
To unsubscribe or ch
Maybe you could leave the current socket and use a new one for your next
attempt? Then simply free the old one when it finishes the connect
(probably with a winsock connection timeout error).
Dan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Max Terent
Somebody else requested that the debug messages be conditionally defined so
you can probably expect that soon.
As for the problem, I think you could just turn off range checking for your
project for the time being.
Dan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] O
On 8/2/06, Francois PIETTE <[EMAIL PROTECTED]> wrote:
> > 008d7c34 +064 REMINDER.EXE OverbyteIcsWndControl 525 +1
> > TIcsWndControl.Dispose
>
> Can you point the exact source code ? It is likely that your line numbers
> doesn't match my line numbers. Show the offending line and a few before and
> 008d7c34 +064 REMINDER.EXE OverbyteIcsWndControl 525 +1
> TIcsWndControl.Dispose
Can you point the exact source code ? It is likely that your line numbers
doesn't match my line numbers. Show the offending line and a few before and
after so that we can locate exactly which istruction trigger
I got the following error report at one customer site which appears to
be during the creation of my TDataModule the TWSocket resides on.
exception class : ERangeError
exception message : Range check error.
Main ($fff9384b):
008d7c34 +064 REMINDER.EXE OverbyteIcsWndControl 525 +1 TIcsWndContro
Hello Max,
> After it I start New smtp session and call SmtpCli->Connect() for next
> email. I receive 10004 in SmtpRequestDone.
> Please note: after TimeOut and SmtpCli->Abort() i receive 10004 error for
> next 20-30 Connect attempts !
10004 is interrupted system call. Possible you get this with
Hello, Francois,
I call SmtpCli->Connect(). If it's timed out - I call SmtpCli->Abort().
After it I start New smtp session and call SmtpCli->Connect() for next
email. I receive 10004 in SmtpRequestDone.
Please note: after TimeOut and SmtpCli->Abort() i receive 10004 error for
next 20-30 Connect
> *Subject:* [twsocket] Connect() time out
> *From:* "Max Terentiev" <[EMAIL PROTECTED]>
> *To:* "ICS support mailing"
> What is proper way to cancel Connect() by timeout ?
You can not cancel a pending connection attempt. All you can do is
changes Windows registry settings to reduce the timeou
> How to cancel SmtpCli->Connect() call if this connection attempt
> is timed out ?
>
> If SmtpCli->Connect() terminated by SmtpCli->Abort() - I notice MANY
> 10004 errors during next connection attempts.
Abort is the way to go. It close the socket at winsock level.
Which winsock call is producin
Hello,
How to cancel SmtpCli->Connect() call if this connection attempt
is timed out ?
If SmtpCli->Connect() terminated by SmtpCli->Abort() - I notice MANY
10004 errors during next connection attempts.
Maybe it's needed to call some Winsock API function directly on
SmtpCli->CtrlSocket ?
What is
13 matches
Mail list logo
