WebException, SSL, System.ComponentModel.Win32Exception

4 Sep 2006 10:30 AM

edmarw

Hi,

Just for information, might help someone:

One of our partners installed a new SSL certificate, and suddenly our
HTTPS connections to them using C# .NET 1.1, started failing with this
exception:

---> System.Net.WebException:
The underlying connection was closed: Could not establish secure
channel for SSL/TLS.
---> System.ComponentModel.Win32Exception:
The function completed successfully, but must be called again to
complete the context
--- End of inner exception stack trace ---

We searched the Web and Google Groups quite a bit, but it took a long
while to find a solution. Taking a hint from
http://www.experts-exchange.com/Programming/Programming_Languages/C_Sharp/Q_21254792.html
, we set

HttpWebRequest request;
// Instantiate request, blabla
request.AllowAllowWriteStreamBuffering = true; // This is what fixed
it.
// Make request, blabla

Anyway, just thought it might help.

Cheers,

Edmar

5 Sep 2006 8:58 PM

Jon Meyer

Make sure that you have the root CA public cert of their CA installed on
your machine. And verify that your partner has your root CA public cert
installed on their machine. That would be the first step I would take. I
believe since you are using .Net 1.1 it doesn't automatically check the CRL.
But if it is checking the CRL then you need to be sure it is publicly
published and available.

-Jon

<edm***@gmail.com> wrote in message
Show quote

news:1157365856.345277.105520@74g2000cwt.googlegroups.com...
> Hi,
>
> Just for information, might help someone:
>
> One of our partners installed a new SSL certificate, and suddenly our
> HTTPS connections to them using C# .NET 1.1, started failing with this
> exception:
>
> ---> System.Net.WebException:
> The underlying connection was closed: Could not establish secure
> channel for SSL/TLS.
> ---> System.ComponentModel.Win32Exception:
> The function completed successfully, but must be called again to
> complete the context
> --- End of inner exception stack trace ---
>
> We searched the Web and Google Groups quite a bit, but it took a long
> while to find a solution. Taking a hint from
> http://www.experts-exchange.com/Programming/Programming_Languages/C_Sharp/Q_21254792.html
> , we set
>
> HttpWebRequest request;
> // Instantiate request, blabla
> request.AllowAllowWriteStreamBuffering = true; // This is what fixed
> it.
> // Make request, blabla
>
> Anyway, just thought it might help.
>
> Cheers,
>
> Edmar
>