none
Server was unable to process request RRS feed

  • Question

  • We are trying to call a third party web service from our app but we are getting the below error on each call.

    However, when we call this third party service from our app when it resides on our Intranet server, the third party service returns the data immediately.

    Why can we call this third party service from our intranet server but when we push our code to Production(DMZ), we get the below error?

    System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.ServiceModel.EndpointNotFoundException:
     There was no endpoint listening at <third party URL> that could accept the message. This is often caused by an incorrect address or SOAP action.
     See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> 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 IP
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
       at System.Net.HttpWebRequest.GetRequestStream()
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       --- End of inner exception stack trace ---

    Sunday, August 10, 2014 4:22 AM

Answers

  • A gateway computer either at your company or the server company has a firewall that is blocking the port number.  Usually HTTP will use port 80 or port 8080 as the common port number but any port number can be used.  Firewalls often just block the well known port number under 1024 but in some companies all ports will be blocked.


    jdweng

    Sunday, August 10, 2014 9:00 AM

All replies

  • We are trying to call a third party web service from our app but we are getting the below error on each call.

    However, when we call this third party service from our app when it resides on our Intranet server, the third party service returns the data immediately.

    Why can we call this third party service from our intranet server but when we push our code to Production(DMZ), we get the below error?

    System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.ServiceModel.EndpointNotFoundException:
     There was no endpoint listening at <third party URL> that could accept the message. This is often caused by an incorrect address or SOAP action.
     See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> 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 IP
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
       at System.Net.HttpWebRequest.GetRequestStream()
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       --- End of inner exception stack trace ---

    Sunday, August 10, 2014 4:21 AM
  • A gateway computer either at your company or the server company has a firewall that is blocking the port number.  Usually HTTP will use port 80 or port 8080 as the common port number but any port number can be used.  Firewalls often just block the well known port number under 1024 but in some companies all ports will be blocked.


    jdweng

    Sunday, August 10, 2014 9:00 AM