Context expired (SEC_E_CONTEXT_EXPIRED?)

• Previous message: Cor Ligthert: "Re: Validating a valid URL"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Wed, 29 Sep 2004 17:38:56 +0200

Hi all,

my apologies if a similar question/problem has been posted before, but a
search of microsoft.public.dotnet.* didn't turn up anything relevant.

At issue is a .Net application using SOAP Web Services, connecting to a
JBoss server over ssl. In almost all circumstances this works fine, but
on one particular computer we're having a problem. Almost exactly 25
seconds after the connection is initiated, it fails (w/o any data
received) with the error message (translated from Norwegian): "The
context has expired and can no longer be used". I take this to be the
SEC_E_CONTEXT_EXPIRED win32 error, but I can't really be certain.
Connecting to the site, displaying the WSDL etc. using Internet Explorer
works fine.

Some details:
Client: Compiled with Visual Studio 2002, running on .Net Framework 1.1,
no service pack. The OS is WinXP Pro sp1.
Server: JBoss 3.0.3 running on Java 1.4.1, SSL Certificate provided by
Comodo Group Inc through InstantSSL.com. Server OS Win2k Server.
Connection: Dialup to dedicated modem farm at colo provider.

I've tried adding a certificate policy to check for certificate errors,
as recommended for similar problems, but I can't see anything wrong
there. I suspect that the validator proc doesn't even get called before
the app crashes, however I've only had phone reports of this so I'm not
sure.

The start of the stack trace (typed in from a printout, beware of typos)
is as follows:

System.Net.WebException: The underlying connection was closed: Could not
establish secure channel for SSL/TLS. --->
System.ComponentModel.Win32Exception: [Norwegian for "The Context etc..."]
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpProtocol.Invode(String
methodName, Object[] parameters)
[snip: SOAP Proxy method, event trace]

Sorry for the long post, but I've tried to add all possibly relevant
details to the rather simple question of why this fails. Any help,
hints, answers or ideas are most welcome.

Thanks in advance

Stig Dommarsnes
Machina AS, Norway

• Previous message: Cor Ligthert: "Re: Validating a valid URL"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]