469,599 Members | 2,893 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

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

Failure Sending a Fault: System.Net.Sockets.SocketException

Hi!

I have a service and client that use WSE 2.0 and soap.tcp. Both are behind
firewalls. Client connects to a public machine's tcp port which is
redirected to service.

If I send a request to service, it is received, but I can't get the
answer.
Here is the message from event log:

Event Type: Error
Event Source: Microsoft WSE 2.0
Event Category: None
Event ID: 0
Date: 2/22/2005
Time: 10:20:38 AM
User: N/A
Computer: kups
Description:
Failure Sending a Fault: System.Net.Sockets.SocketException: A connection
attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has
failed to respond
at Microsoft.Web.Services2.Messaging.SoapTcpConnectio n.Connect()
at Microsoft.Web.Services2.Messaging.SoapTcpConnectio n..ctor(Uri
remoteEndpoint, SoapTcpTransportOptions options, ISoapFormatter formatter)
at Microsoft.Web.Services2.Messaging.SoapTcpTransport .GetConnection(Uri
destination)
at
Microsoft.Web.Services2.Messaging.SoapTcpOutputCha nnel.Send(SoapEnvelope
message)
at Microsoft.Web.Services2.Messaging.SoapReceiver.Sen dFault(SoapEnvelope
request, Exception ex)
What could be the problem?

Kristjan
Nov 23 '05 #1
2 3050
It sounds like the port that you come in on is open, but you can't get back
out on that port.
Hi!

I have a service and client that use WSE 2.0 and soap.tcp. Both are
behind firewalls. Client connects to a public machine's tcp port
which is redirected to service.

If I send a request to service, it is received, but I can't get the
answer. Here is the message from event log:

Event Type: Error
Event Source: Microsoft WSE 2.0
Event Category: None
Event ID: 0
Date: 2/22/2005
Time: 10:20:38 AM
User: N/A
Computer: kups
Description:
Failure Sending a Fault: System.Net.Sockets.SocketException: A
connection
attempt failed because the connected party did not properly respond
after a
period of time, or established connection failed because connected
host has
failed to respond
at Microsoft.Web.Services2.Messaging.SoapTcpConnectio n.Connect()
at Microsoft.Web.Services2.Messaging.SoapTcpConnectio n..ctor(Uri
remoteEndpoint, SoapTcpTransportOptions options, ISoapFormatter
formatter)
at
Microsoft.Web.Services2.Messaging.SoapTcpTransport .GetConnection(Uri
destination)
at
Microsoft.Web.Services2.Messaging.SoapTcpOutputCha nnel.Send(SoapEnvelo
pe
message)
at
Microsoft.Web.Services2.Messaging.SoapReceiver.Sen dFault(SoapEnvelope
request, Exception ex)
What could be the problem?

Kristjan


Nov 23 '05 #2
The error occured due to client-side timeout which came earlier than server
time-out. So, the client did not accept the fault message.

Nov 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by paulbubach | last post: by
2 posts views Thread by Steve Lowe | last post: by
1 post views Thread by larspeter | last post: by
2 posts views Thread by Danny | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.