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

An Unexpected Error Occurred On A Receive .net 3.5

The issue I am left with is on my development machine which requires .Net framework 1.1 to run VB.Net 2003. http://support.microsoft.com/kb/295626 EDIT: Noticed the link above is somewhat out of date. i.eXmlDocument xdoc = new XmlDocument();xdoc.Load(fs);by the i am using NET 1.1 and VS 2003. I’m sure server side doesn’t give any error it works fine.   Below given is the entire error message displayed on page.     The underlying connection was closed: An unexpected have a peek here

Left by Skott on Jun 01, 2010 7:20 AM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. Of the threaded webservice I've written, I didn't encounter this issue because I was interacting with a propriatary webservice. application pool recycling or crashes that interrupt logic that may be runnning. 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 http://stackoverflow.com/questions/3197010/httpwebrequest-getresponse-the-underlying-connection-was-closed-an-unexpected

I noticed that this error ("The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.") started to appear after we migrated our Is there any way to identify who shut down the connection? So issue still persists even after installing 4.6 framework. Hope that helps...

Everyone,I recommend you check out AskF5's explaination on this issue as it has fixed our "The underlying connection was closed: An unexpected error occurred on a receive." error. Can you see if you can repro the issue with the standalone implementation at http://www.codeproject.com/KB/IP/remotingcompression.aspx? We are using 2 F5 Big-Ip. Disabling "Accept client certificates" allowed the page to load normally.

Left by Mark David on Oct 09, 2008 4:00 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. I have added some of the suggestions above and will see if it has any effect. Browse other questions tagged c# httpwebrequest timeout getresponse or ask your own question. I received an error "The underlying connection was closed: An unexpected error occurred on a send." when I run the same piece of code on the server where Windows Server 2008

Left by fer on Oct 20, 2008 6:37 AM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. I need help with negotiation Religious supervisor wants to thank god in the acknowledgements Did Donald Trump call Alicia Machado "Miss Piggy" and "Miss Housekeeping"? I had this same issue in a windows application I wrote. How often does this happen?

That said after successfully running this without one error in just under a month ... Make a suggestion Dev centers Windows Office Visual Studio Microsoft Azure More... The endpoints I was originally trying to connect to didn't support TLS 1.2 which gave the original error message, luckily they had another server which did provide TLS1.2 and I connected Does anyone think that the part of the error text 'an unexpected error ...on RECEIVE' is significant?

Probably you are getting block because the User-Agent is empty.Set the User-Agent with something in the Request HeaderThat words for me Example:webClientRetriever.Headers.Add("User-Agent", "MyProject"); Left by Jkalderonkiros on Jan 05, 2010 10:38 navigate here Acácio SolutionDislike(0)Like(0)Dislike(0)Like(0)Chris O'ReillyPosted on 26 FebChris O'ReillyRank: #3225Posted on 26 FebSolutionHelloAcácio, Wow, what a quick reply, thanks. at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, If another OutSystems Platform is on the receiving end (meaning: the web call is to an OutSystems Platform) you may want to look here.

Check maybe the inner exception for more details if not done already... ‹ Previous Thread|Next Thread › This site is managed for Microsoft by Neudesic, LLC. | © 2016 Microsoft. This may reduce the likelyhood of this error occuring but would not stop the error. You’ll be auto redirected in 1 second. http://dukesoftwaresolutions.com/an-unexpected/the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-receive-wcf.html Is this the same issue, I mean the Keep Alive being set to true by default?

UI performance with large image data Is 8:00 AM an unreasonable time to meet with my graduate students and post-doc? And then it magically works again.So, possibly there is some connection to the database that is stuck open that is closed when the database is deleted. Please, this is very urgent.i have a mobile application that access to a web service.some times it returns the error: (i don’t know what to do)windows mobile system.net.webexception: unable to read

How to deal with a very weak student?

Left by Taytay on Mar 20, 2007 9:54 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. hi. Is that a server that you control? –Rebecca Chernoff Jul 7 '10 at 17:48 I have no control over the receiving server -- the only one I have access Posted on Tuesday, August 16, 2005 2:31 PM | Back to top Comments on this post: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. # re:

How to solve this issue? Any suggestion in resolving the issue? This request can be a: Web service call (SOAP or REST) A request to a specific web-page Sending an email ... this contact form Train carriages in the Czech Republic I lost my jury summons, what can I do?

This does not indicate to me that it is a bug in IIS, but I am still stumped. Is the receiving server even IIS? I'm concerned about the performance issues involved in reconnecting, however I have written my code to keep most connections and data transfer small anyways, I'll have to keep an eye on Setting the KeepAlive and ProtocolVersion properties of the HttpWebRequest instance solved the issue.

Left by Wade on May 23, 2008 11:18 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. very nice article Left by hello on Sep 04, 2011 11:49 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. Client needs to send one request with fixed frequency say 5-min. Another question: the close of connection is carried out by outsystems server or the server the API calls ?

I had one web service with only one method and i was receiving this error anytime i called the method from a windows client. If you are using Microsoft Visual C#, the new method must be similar to the following. I doubt it, though. Left by plclogic on Feb 08, 2007 7:11 PM # re: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.

Is it necessary? In particular, it's difficult to see how object complexity could cause a networking error. We are, however, still getting the same error with much lower frequency. Others work normally.The only solution I have that works is to completely delete the entire database and then recreate a new database and repopulate.