desperate call for help: "The underlying connection was closed: Unable to connect to the remote ser

[David]

I have a web service running on a server.

With my brower, I can get the asmx page and get the expected output on the
page.

With a console application, I can call the webservice and retrieve from it
what I am supposed to retrieve.

Only when an ASP.NET application calls the web service, do I get the "the
underlying connection was closed: Unable to connect to the remote server"
error message.

The only relevent msdn page
(http://support.microsoft.com/default.aspx?scid=kb;en-us;819450) isn't very
helpful. It says MS has confirmed it as a bug, and says to contact them
for a fix!!!! And there might be a charge! ARE YOU KIDDING ME?

The last time I contacted them, it was like talking to a wall.

Thanks. Any help would be greatly appreciated.

 

[Dan Rogers]

Hi David,

Have you tried setting the proxy-side keep alives to "false"? This may
remedy the situation.

Dan Rogers
Microsoft Corporation
--------------------

From: "David" <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
Subject: desperate call for help: "The underlying connection was closed:

Unable to connect to the remote server.

 

[David]

Is that a IIS setting?

Do you mean HTTP Keep-Alives enabled? I tried that and it still does not
work.

 

[Dan Rogers]

Hi David,

No, not on the IIS side. On the proxy side. In the proxy that was
generated when you did an add-web-reference, there is a setting that
governs when/if the proxy requests a keep alive.

I hope this helps

Dan Rogers
Microsoft Corporation
--------------------

From: "David" <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
References: <[email protected]>

Subject: Re: desperate call for help: "The underlying connection was

closed: Unable to connect to the remote server.