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
http://weblogs.asp.net/jan/archive/2...08/128394.aspx ("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
part:
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;
proxyPeticionSincrona.Credentials=
System.Net.CredentialCache.DefaultCredentials;
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:
System.Net.ServicePointManager.CertificatePolicy
= new AcceptAllCertificatePolicy();
which should be enough, I guess. It returns true on
CheckValidationResult.
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:
<configSections>
<section name="microsoft.web.services"
type="Microsoft.Web.Services.Configuration.WebServ icesConfiguration,
Microsoft.Web.Services, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>
<microsoft.web.services>
<diagnostics>
<trace enabled="true"
input="inputTrace.config"
output="outputTrace.config"/>
</diagnostics>
</microsoft.web.services>
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
look?
Thanks in advance.
--
David Mediavilla
