In case this helps someone track down a silly little defect…

I have an orchestration that uses an outbound map on a send port.  The map had a script shape that had incorrect xslt.  Simply running the Test Map would have caught this one and saved me some time. 

The full detail of the Exception Message (tracked via the Orchestation Debugger –> Show Tracked Exceptions):

Microsoft.XLANGs.Core.XlangSoapException: An error occurred while processing the message, refer to the details section for more information
Message ID: {4C5A6C53-46B7-46FA-9501-86F6462374B0}
Instance ID: {46EF83ED-3DDD-4B33-972E-93C80FE4D06A}
Error Description: Exception from HRESULT: 0x80131942
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env, Int32 operationId, Context ctx)
   at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelope& env, Boolean topOnly)
   at Microsoft.XLANGs.Core.PortBase.GetMessageIdForSubscription(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
   at MyOrchestration.WithAMap.segment1(StopConditions stopOn)
   at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Microsoft.XLANGs.Core.XlangSoapException