Re: Web Service timeout

From: Paul Degneau (ytivarg_at_ivggzn.net)
Date: 03/11/04 

Date: Thu, 11 Mar 2004 17:14:45 -0600

Well...I think I'm getting closer. I tried out a 2k client box, I got
better error messages:

System.Net.WebException: The underlying connection was closed: An unexpected
error occurred on a send.
   at
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request)
   at
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebReques
t request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
   at SimpleClassLib.SimpleWebService.Service1.HelloWorld()
   at SimpleClassLib.Class1.getModROSNom()

System.Net.WebException: The underlying connection was closed: An unexpected
error occurred on a receive.
   at
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request)
   at
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebReques
t request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
   at SimpleClassLib.SimpleWebService.Service1.HelloWorld()
   at SimpleClassLib.Class1.getModROSNom()

Googling on these errors returned an ASP.NET bug
http://support.microsoft.com/default.aspx?scid=kb;en-us;819450. The
client-side workaround described seems to work, but only if I use anonymous
access for my web service. This is a medical application and we will be
required to use Integrated Windows Auth at a minimum. Is there any other
workaround for this problem? What is the timeframe for 1.1 SP1?

I still don't understand why this problem doesn't occur at all with IIS 5.0
or 5.1. I also don't understand why I get differing error messages from XP
and 2k.

Thanks
Paul

"Paul Degneau" <ytivarg@ivggzn.net> wrote in message
news:OFPOCd3BEHA.3404@TK2MSFTNGP10.phx.gbl...
> I've started sniffing the traffic between the client and server and when
the
> timeouts occur there is no traffic at all. Could IE be causing problems
> even before the request is sent? If so, why don't we see this problem when
> we use IIS5 or IIS5.1? Any ideas? I'm open to anything at this point.
>
> Thanks
>
>

Relevant Pages

  • The underlying connection was closed - Remoting.Channels.Http.HttpClientTransportSink
    ... Web Services Client: ... closed: The request was c ... >System.Net.WebException: The underlying connection was ...
    (microsoft.public.dotnet.framework)
  • Re: breaking the model
    ... > The forms data then is in the Request object. ... HTTP Request; in this case, the form POST Request from the Page. ... client and server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Resolving record with enumerated type
    ... In a CPU BFM package, ... because data goes in two directions (request from the ... from the server to the client), you'll need some way to orchestrate ...
    (comp.lang.vhdl)
  • Re: WSE 3.0 + UserNameToken without X.509 Cert/Kerberos + Signing + Encryption How?
    ... I still think that there is a lot of benefit for Secure Conversation ... message security and thefore it does not encrypt the message. ... between client and server using a UserNameToken that passes the UserName ... assuming the client request adds a proper UserNameToken... ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • RE: Problems with wsdl-generated proxy clients
    ... the client gets the same error on my xp ... meaning that the request was malformed. ... Microsoft MSDN Online Support Lead ... Looking at the IIS logs, I didn't even see the request in the log. ...
    (microsoft.public.dotnet.framework.webservices)