Arno
You are correct - Microsoft Windows Server 2008 R2 is 64-Bit Only
You could get Microsoft Windows Server 2008 in 32-Bit or 64-Bit.
Mark Moss
- Original Message -
From: twsocket-requ...@elists.org
To: twsocket@elists.org
Sent: Saturday, December 25, 2010 5:00 AM
Subject: TWSocket Digest, Vol 404, Issue 6
Send TWSocket mailing list submissions to
twsocket@elists.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
or, via email, send a message with subject or body 'help' to
twsocket-requ...@elists.org
You can reach the person managing the list at
twsocket-ow...@elists.org
When replying, please edit your Subject line so it is more specific
than Re: Contents of TWSocket digest...
Today's Topics:
1. Re: 10053 error occurring only on Win2008 (SP2) and not
onWin7 (Fastream Technologies)
2. Re: 10053 error occurring only on Win2008 (SP2) and not
onWin7 (Arno Garrels)
3. Re: 10053 error occurring only on Win2008 (SP2) and not
onWin7 (Fastream Technologies)
--
Message: 1
Date: Sat, 25 Dec 2010 11:36:10 +0200
From: Fastream Technologies ga...@fastream.com
Subject: Re: [twsocket] 10053 error occurring only on Win2008 (SP2)
and not onWin7
To: ICS support mailing twsocket@elists.org
Message-ID:
aanlkti=j7nirydhswgpddthwmos08vsot=v4iuaol...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
Hello Francois,
I already knew that but it also happens when the connection is between
local
ICS SSL client and server. I have no idea how this could be prevented?
Also sometimes the client returns no 10053 but StatusCode = 0!
Regards,
SZ
On Sat, Dec 25, 2010 at 11:25 AM, Francois PIETTE
francois.pie...@skynet.be
wrote:
Error 10053 is WSAECONNABORTED.
Software caused connection abort.
An established connection was aborted by the software in your host
computer, possibly due to a data transmission time-out or protocol error.
http://msdn.microsoft.com/en-us/library/ms740668(v=vs.85).aspx
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
- Original Message - From: Fastream Technologies
ga...@fastream.com
To: ICS support mailing twsocket@elists.org
Sent: Saturday, December 25, 2010 8:24 AM
Subject: [twsocket] 10053 error occurring only on Win2008 (SP2) and not
onWin7
Hello,
With the HttpCli, I get 10053 when lots of consecutive POSTs are made
with
SSL. I first thought it is related to the 4096 bit self-signed cert we
used
but it does not happen on Win2008. The test machine is remote (in the
Netherlands) and when I run the GUI (web client) from here on my Win7,
it
works as expected. It also works if I run it against the same ICS web
server
on localhost. But when I run the client on Win2008 remotely on RDP, it
crashes! Since all but all customers use Win2008, I need some help with
this!
Happy holidays to all of you!
SZ
--
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
--
Message: 2
Date: Sat, 25 Dec 2010 11:43:45 +0100
From: Arno Garrels arno.garr...@gmx.de
Subject: Re: [twsocket] 10053 error occurring only on Win2008 (SP2)
and not onWin7
To: ICS support mailing twsocket@elists.org
Message-ID: 6a567ab4c8e54394b3f13becc79c2...@asus
Content-Type: text/plain; charset=iso-8859-1
Fastream Technologies wrote:
Hello,
With the HttpCli, I get 10053 when lots of consecutive POSTs are made
with SSL. I first thought it is related to the 4096 bit self-signed
cert we used but it does not happen on Win2008.
So it works on 2008?
The test machine is
remote (in the Netherlands) and when I run the GUI (web client) from
here on my Win7, it works as expected. It also works if I run it
against the same ICS web server on localhost. But when I run the
client on Win2008 remotely on RDP, it crashes!
So it crashes on 2008?
Any error message, stack trace etc.?
Isn't server 2008 SP2 64-bits only?
--
Arno Garrels
--
Message: 3
Date: Sat, 25 Dec 2010 13:05:32 +0200
From: Fastream Technologies ga...@fastream.com
Subject: Re: [twsocket] 10053 error occurring only on Win2008 (SP2)
and not onWin7
To: ICS support mailing twsocket@elists.org
Message-ID:
aanlktinkjs9wyyodyffrerdevkujgrgh4rs3f670=...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
Dear Arno,
It does work on Win7 but does NOT work on Win2008 and Win2008R2. It works
perfectly with NO SSL on all Windows. The HTTP client does not raise any
exception--just 10053 and StatusCode=0 issues. I have uploaded the
cert/pkey
at,
http://www.fastream.com/ics/certpkey.zip
It is a 4096-bit self-signed cert for testing. It works for 8-10 POSTs
then
