Assume that you create an itinerary to dynamically route a message to an email address by using a Lightweight Directory Access Protocol (LDAP) query in Microsoft BizTalk Server 2009 or 2010. In this situation, the email message is not delivered, and you receive an error message that resembles the following:
There was a failure executing the receive pipeline:
"Microsoft.Practices.ESB.Itinerary.Pipelines.ItineraryReceiveXml, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Dispatcher Disassemble" Receive Port: "OnRamp.Itinerary" URI: "/ESB.ItineraryServices/ProcessItinerary.asmx" Reason: Transport location could not be resolved from the resolver string
"Microsoft.Practices.ESB.Itinerary.Pipelines.ItineraryReceiveXml, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Dispatcher Disassemble" Receive Port: "OnRamp.Itinerary" URI: "/ESB.ItineraryServices/ProcessItinerary.asmx" Reason: Transport location could not be resolved from the resolver string