none
ESB All Exception port issue RRS feed

  • Question

  • We are getting the snap in error while opening the admin and at the event log the following is the error message got logged. But all other servers are woring.

    There was a failure executing the send pipeline: "Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor, Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Transform" Send Port: "ALL.Exceptions" URI: "SQL://SQL\db1/EsbExceptionDb/" Reason: Error 175002: An unexpected error occurred while trying to execute the map, 'Microsoft.Practices.ESB.ExceptionHandling.Maps.FaultMessage_to_ExceptionSql, Microsoft.Practices.ESB.ExceptionHandling.Maps, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.


    SenthilKumar R Please Mark as Answered if answers your question


    Wednesday, September 26, 2012 10:02 AM

Answers

  • Hi,

    It looks like the ESB Toolkit can't execute the "FaultMessage_to_ExceptionSql" map. Maybe the suspended message (Faultmessage) is empty?

    An option is to save the suspended message and execute the FaultMessage_to_ExceptionSql map with a tool outside BizTalk. Then you can see if the suspended message is the problem,.

    You can download the BizTalk.MapTester tool from:

     http://code.msdn.microsoft.com/Execute-a-BizTalk-map-from-26166441

    The tool needs an XML message and the name of the map in BizTalk

    Name: Microsoft.Practices.ESB.ExceptionHandling.Maps.FaultMessage_to_ExceptionSql
    Assembly: Microsoft.Practices.ESB.ExceptionHandling.Maps, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

    greetings,

    Tomasso Groenendijk

    Wednesday, September 26, 2012 12:21 PM

All replies

  • Hi,

    It looks like the ESB Toolkit can't execute the "FaultMessage_to_ExceptionSql" map. Maybe the suspended message (Faultmessage) is empty?

    An option is to save the suspended message and execute the FaultMessage_to_ExceptionSql map with a tool outside BizTalk. Then you can see if the suspended message is the problem,.

    You can download the BizTalk.MapTester tool from:

     http://code.msdn.microsoft.com/Execute-a-BizTalk-map-from-26166441

    The tool needs an XML message and the name of the map in BizTalk

    Name: Microsoft.Practices.ESB.ExceptionHandling.Maps.FaultMessage_to_ExceptionSql
    Assembly: Microsoft.Practices.ESB.ExceptionHandling.Maps, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

    greetings,

    Tomasso Groenendijk

    Wednesday, September 26, 2012 12:21 PM
  • Thanks, still valid in 2017 :) I was testing ESB with empty suspended messages.
    Thursday, November 2, 2017 9:43 AM