When using ESB Toolkit’s Exception Management WCF service in .NET Applications to submit faults to the Esb Management Portal. You might see the below errors in the event log of the server where BizTalk and Esb Toolkit are installed


A message sent to adapter “SQL” on send port “ALL.Exceptions” with URI “SQL://<server name>/EsbExceptionDb/” is suspended. 
 Error details: There was a failure executing the send pipeline: “Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor, Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “ESB BAM Tracker” Send Port: “ALL.Exceptions” URI: “SQL://<servername>/EsbExceptionDb/” Reason: Error 125006: The BAM Activity Id could not be found in the Fault message using the xpath : xpath  
 MessageId:  {7D272E10-5655-4063-8D70-D1AB6ABBFDE9}
 InstanceID: {B65710D2-2F2B-4A4F-A38B-77F90978E1F8}

and 

There was a failure executing the send pipeline: “Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor, Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “ESB BAM Tracker” Send Port: “ALL.Exceptions” URI: “SQL://<server name>/EsbExceptionDb/” Reason: Error 125006: The BAM Activity Id could not be found in the Fault message using the xpath : xpath“.

If you see the above errors, all you have to do is,
  1. Open the BizTalk Admin console
  2.  Navigate to the application called “Microsoft.Practices.ESB”
  3. In the application navigate to the send port called “All.Exceptions”
  4. Open properties of the send port, click the ellipses against the Send Pipeline called “ESBFaultProcessor”. The ellipses in highlighted in the image below
     
     5.  After clicking the ellipses, under the “Component(2): ESB BAM Tracker”, Make Enabled “False”. It is set to “True” by default. As highlightd in the below image
     6. Click Ok twice and restart the host instances
The above mentioned steps should fix the errors, and you will be able to use ESB Toolkit’s Exception Management WCF service in .NET Applications to submit faults to the Esb Management Portal. Happy BizTalking!!!