SOAP error not able to handle in Exception Handler block RRS feed

  • Question

  • Failing at Request Response Send port but not coming to Exception Handler.
    I used Scope Transaction Type as None, Retry counts is set 0 on Send Port, and after Scope choose Exception Handler of Object Type as System.Exception, the Orchestration is Suspended (Resumable).
    Why is the error not able to come to Exception Handler. Please advise

    Error details: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at that could accept the message

    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 


    • Edited by Dan2890 Monday, October 19, 2020 9:04 PM a
    Monday, October 19, 2020 9:04 PM

All replies

  • It is coming to Exception block, but the System.Exception object type is showing as empty.

    Not sure why System.Exception is not able to handle or grab the error.

    The Orch is suspended resumable, in the event logs I see the error....but still System.Exception is not able to capture the error

    Anyone please advise


    Tuesday, October 20, 2020 5:14 PM
  • Can you share the code that is in the shapes in the Exception block?

    Is the Orchestration suspending?  If so with what error?

    Tuesday, October 20, 2020 7:34 PM
  • Tried individually all below three, but none of them are giving description of error. It is coming as empty
    Ex1 is is of Object Type System.Exception
    Ex is variable of type String

    Ex = Ex1.InnerException.ToString(); ---->doesnt work

    Ex = Ex1.Message; ----> doesnt work

    Ex = Ex1.Message.ToString(); ----> doesnt work

    When I try to write in logs, it is coming as System.Exception : 


    Tuesday, October 20, 2020 7:53 PM
  • Strange Ex1.Message; should have worked

    Ex1.InnerException.ToString(); would sometimes cause an issue as there sometimes isn't a InnerException.

    Have you tried Ex1.ToString(); to see if there is anything in the exception at all?

    Wednesday, October 21, 2020 12:57 AM
  • Hello,

    You need to expand beyound using system exception, add additional catch exception block  and use an explicit  soap exception catch:

    System.Web.Services.Protocols.SoapException - This is going to to be your new exception type.

    Please try this, Good Luck!

    Regards PK: Please mark the reply as answer or vote it up, as deemed fit.

    Tuesday, October 27, 2020 1:30 AM