By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,212 Members | 2,209 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,212 IT Pros & Developers. It's quick & easy.

"An unexpected error occurred on a receive" with WSE 1.0 and HTTPS

P: n/a
I am writing a client for an HTTPS web service using WSE 1.0 but I
always get an error like "The underlying connection was closed: An
unexpected error occurred on a send."
Sometimes the error "occured on a receive".

Looking around, I find ("Solving
"The underlying connection was closed" when using WSE"), that sets
KeepAlive to false, but it doesn't work for me since when I get to the

System.Net.WebRequest request
= base.GetWebRequest(uri);

I always get NullReferenceException.

Anyway that solution seemed to be for cases when there was an
occasional accummulation of requests. In this case, I am only sending
one request, the server (which I don't control) is probably not busy,
and I get the error every time.

Other things I have tried are:

proxyPeticionSincrona.UnsafeAuthenticatedConnectio nSharing= true;
proxyPeticionSincrona.PreAuthenticate= true;

but they make no difference.

When I try the service from a browser I get questioned about the
certificate (its authority is not recognized and it is for another
machine) but after accepting the dialogs it shows me a SOAP fault. My
client can't reach the fault stage.
I take care of the certificates with:

= new AcceptAllCertificatePolicy();

which should be enough, I guess. It returns true on

I am using WSE 1.0 SP1. I have also installed Service Pack 1 for .NET
1.1 but it made no difference.

I have tried to activate the WSE trace in my web.config:

<section name=""

type="Microsoft.Web.Services.Configuration.WebServ icesConfiguration,
Microsoft.Web.Services, Version=, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />

<trace enabled="true"

but these .config files appear nowhere.

I have an equivalent client in Java that runs OK.
I also have another WSE 1.0 client (unfortunately, I only have the
binaries) for this service that is getting these same errors and also
one about not establishing a secure channel for SSL/TLS. This client
worked from another part of the intranet, so it could be a problem of
configuration, but I cannot figure what it would be.

Has anyone had a similar experience? Can you point me somewhere to

Thanks in advance.
David Mediavilla

Nov 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.