469,568 Members | 1,676 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,568 developers. It's quick & easy.

Unable to write data to the transport connection & Timeout

We are continually receiving timeout, and "Unable to
write data to the transport connection" errors while using the
System.Net.HttpWebRequest class from an ASP.Net web page. Below are the two
errors we continue to
receive:

Source: System
Message: The operation has timed-out.
Target Function: System.Net.WebResponse GetResponse()

Stack Trace:
at System.Net.HttpWebRequest.GetResponse()
at Transaction.Process()

and

Source: System
Message: Unable to write data to the transport connection.
Inner Exception: System.IO.IOException: Unable to write data to the
transport connection. ---> System.Net.Sockets.SocketException: An
established connection was aborted by the software in your host machine
at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32 offset, Int32
size, SocketFlags socketFlags, AsyncCallback callback, Object state)
at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32 offset,
Int32 size, AsyncCallback callback, Object state)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32 offset,
Int32 size, AsyncCallback callback, Object state)
at System.Net.TlsStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size,
AsyncCallback asyncCallback, Object asyncState)
Target Function: System.IAsyncResult BeginWrite(Byte[], Int32, Int32,
System.AsyncCallback, System.Object)

Stack Trace:
at System.Net.TlsStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size,
AsyncCallback asyncCallback, Object asyncState)
at System.Net.Connection.BeginWrite(Byte[] buffer, Int32 offset, Int32 size,
AsyncCallback callback, Object state)
at System.Net.ConnectStream.BeginWrite(Byte[] buffer, Int32 offset, Int32
size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at Transaction.Process()

Do I need to contract out someone to develope a solid socket object that I
can interface with, whether it be .Net or COM? It's critical that these
connections make it through in real-time, and the fact is, that the above
two
errors happen to about 5% of our requests. I have verified that when
requests timeout, it has nothing to do with the receiving party. They never
even receive the request from us. The second error occurs seemingly at
random, and while it usually makes it to the target server, it drops off
before we can receive the response.

Any tips, or advice would be appreciated, and there is nothing between the
server and the internet(no proxies, no web services) other than the firewall
which works perfectly fine.

Thanks,
Steve
Nov 15 '05 #1
0 9523

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by dina_vr | last post: by
2 posts views Thread by Keith Avery | last post: by
reply views Thread by steve.edison | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.