Home > An Unexpected > An Unexpected Error Occurred On A Receive .net 3.5

An Unexpected Error Occurred On A Receive .net 3.5

application pool recycling or crashes that interrupt logic that may be runnning. In this occurance, the connection times out but is not recognized as closed and thus a new connection is not established for the next request and an error is returned. We are using 2 F5 Big-Ip. Browse other questions tagged c# or ask your own question. check over here

You’ll be auto redirected in 1 second. I had the same problem but it was not the KeepAlive that messed it up for me. We'll see if that makes a difference. The suggestions I found indicated that setting the keepalive should solve it, yet some suggested setting the http version to 1.0. http://stackoverflow.com/questions/3197010/httpwebrequest-getresponse-the-underlying-connection-was-closed-an-unexpected

I had this same issue in a windows application I wrote. RSS Reader Blog The horror of no source control Archives November 2011 (1) September 2009 (1) June 2009 (1) October 2008 (2) May 2007 (1) February 2007 (1) January 2007 (2) Officially, the version 1.0 doesn't support keep-alives, however some implementations do support it. .Net is designed to use http 1.1 to make requests which encourages persistant connections. when client gets desired data that frequency is reset to 5-min/(5-min minus time needed to get desired data).

We have this problem also.It seems to only affect certain web services. MS KB Article (Resolution D):http://support.microsoft.com/kb/915599/en-us Left by hB on Dec 09, 2007 1:07 AM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. The failure occurs ~7 minutes after I call request.GetResponse(). Left by Denis Pitcher on Oct 03, 2005 1:05 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.

DataSet quick viewer Convert HTML to Wikipedia format System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. Left by Max on Nov 17, 2005 6:26 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. B-) Gerry Lowry, Chief Training Architect, Paradigm Mentors Learning never ends... +1 705-999-9195 wasaga beach, ontario canada TIMTOWTDI =.there is more than one way to do it Reply Anil12345678 None 0 http://forums.asp.net/t/2079336.aspx?+The+underlying+connection+was+closed+An+unexpected+error+occurred+on+a+send+issue+on+windows+server+2008+SP2+32+bit+OS I have been fighting with problem for awhile...

IIS 6.0 by default sometimes sends an extra HTTP 100 Continue message which by the RFC2616 standard is incorrect. Now we'll try HTTP1.0 as well to see if that makes any difference.... See Error Message 3. –DGibbs Feb 12 '14 at 13:06 add a comment| 2 Answers 2 active oldest votes up vote 6 down vote accepted The underlying connection was closed: An Any suggestion for me?

This is from a poster who was also trying to get .NET 1.1 to interoperate. This suggests that this is not a networking error, despite the exception message you posted. at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at ssExternalWebservices.WRefCarweBVRRWebServiceMain.WRefCarweBVRRWebService.strB2BGetVehicleByVRM(String inWSstrUserName, Boolean inWSstrUserNameSpecified, String inWSstrPassword, Boolean inWSstrPasswordSpecified, String inWSstrClientRef, Boolean inWSstrClientRefSpecified, String inWSstrClientDescription, Boolean inWSstrClientDescriptionSpecified, String inWSstrKey1, Boolean inWSstrKey1Specified, Microsoft has even issued a patch here: http://support.microsoft.com/kb/898708/en-usThe reason why disabling keepalives worked most of the time is it wasn't able to use this continue feature as much.Patch up your IIS

Multiple-Key Sorting What is a plural of "To-Do"? "To-Dos" or "To-Does"? check my blog Analyze the server logs to see if this may be the issue. I've been beating my head on this one for a while. Just paste this into the reference.cs and you're ready to go.

share|improve this answer answered Feb 15 at 17:29 Hugh Jeffner 1,73921517 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign One way to do this is to display Exception.ToString.   There may be useful information that you're ignoring by not looking at the entire exception. And I can manually hit the service from the DMZ by using a browser so I know the DMZ machine can actually get to it. http://svbuckeye.com/an-unexpected/an-unexpected-error-occurred-on-a-receive.php Hello,I have the same problem on calling a web serviceThe underlying connection was closed: An unexpected error occurred on a receive.I applied the fix below as recommended but when I override

Below is the client configuration for remoting: Here's the error stack (full URL disguised) for you to look at, just to add more detail the remote site is using TLS1.0 Regards, Chris. not likely.

His problem was that his service was using platform-specific data, specifically nullable types. .NET 1.1 didn't like that.

Should I include him as author? at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at ssCRMApp.WRefPeopleLookup.WRefPeopleLookup.SearchByName(String search) [2] Unable to read data from the transport connection: An existing connection was Your post help me resolve my issue. Please review the stack trace for more information about the error and where it originated in the code.   Exception Details: System.Net.WebException: The underlying connection was closed: An unexpected error occurred

Thanks for your help and quick responses, and I've learned a lot about error tracing and troubleshooting. You need to get in touch with the provider of the service so they can tell you what's happening. If that fails, I may make an unmanaged call via COM to the dang thing! have a peek at these guys So...I know the service is up and responding to requests.

This means: The base error is "connection was closed while sending information" == because == "the remote party has closed the transport stream [the connection]" By the way, this is a I get the same error message when i try to create a JNDI context. It apparently has nothing to do with the rebooting of the machine that has the service on it. This problem occurs when the server or another network device unexpectedly closes an existing Transmission Control Protocol (TCP) connection.

The underlying connection was closed: An unexpected error occurred on a receive. How to deal with a very weak student? Dennis, You're awesome! Train carriages in the Czech Republic I lost my jury summons, what can I do?

Wish this helps you... i created one console aplication -(,net 2.0)for uploading file from my local system to one ftp site -(,net 2.0)for this i am using the ftp web request(file uploader concept)i am getting Left by Kwasi on Mar 04, 2009 12:56 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. i am calling a method from a webservice and i keep getting the error intermittently.

Left by Jag on Nov 18, 2008 8:53 AM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. Any help would be greatly appreciated.Thanks in advance.Tanweer Left by Tanweer on Jul 29, 2008 3:13 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a