Exception Type: Microsoft.XLANGs.Core.FaultReceive Exception

Hi All,

Several messages are constructed to be sent to the message box.

In another orchestration there is a receive shape that consume the previous messages.

In some messages not all, about 20% i got this exception :

Exception Type: Microsoft.XLANGs.Core.FaultReceiveException

Exception Description: Exceptions.Types.FaultReceiveException

The messages were constructed using an assignment shape : Msg = XMLDoc;

XMLDoc it's a variable of this type : System.Xml.XmlDocument

Receive shape of the orchestration ( Ordered Delivery is set to True )

Thank's;

I'm wondering if this syntax it's the source of problem : Msg = XMLDoc ?

Should i do a convert to string ? like that XMLDoc.toString();

  • Edited by Aheriz Tuesday, January 07, 2014 3:56 PM
January 7th, 2014 6:15pm

Hi Aheriz,

Your Expression seems ok .

Work around of your problem:

You need to look for the messages which are creating you fault Exception .You can create a Fault Port and and redirect the fault message .This will give idea about messageType which is failing in Orchestration .

Thanks

Abhishek

  • Proposed as answer by Abhishek0127 Tuesday, January 07, 2014 5:07 PM
  • Unproposed as answer by Aheriz Tuesday, January 07, 2014 5:18 PM
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2014 8:06pm

The problem is that the received message is clean and only few messages that failed.

when we resubmit them it works, i'm thinking that there is a problem with the XMLDocument because the exception faultString is System.Xml.XmlDocument

January 7th, 2014 8:14pm

HI Aheriz,

You can go to biztalk admin console and look at the Orchestration debugger for those messages which has failed . If possible try to have some tracing over your Orchestration and capture the exact cause of failure .

Thanks

Abhishek

  • Proposed as answer by Abhishek0127 Tuesday, January 07, 2014 5:53 PM
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2014 8:22pm

everything seems correct in case of syntax.

assuming that u are using web or wcf services in ur orchestration and u are not handling the fault exception sent by the service.

create a "new fault message" in ur port by right click on the port operation and then handle the fault message that u are receiving.

Regards

January 8th, 2014 8:33am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics