title: BizTalk Party not being resolved for incoming HL7v2 message
body: <p>I have a BizTalk application which is setup to receive HL7v2 messages on an MLLP receive location.</p>
  
  <p>I've setup parties in order to resolve based on the Sending Application (MSH.3) and apply our local schema to the incoming message type which is ORU_R03_23_GLO_DEF.</p>
  
  <p>So the party is SUPPOSED to be converting the schema from </p>
  
  <pre><code>http://microsoft.com/HealthCare/HL7/2X#ORU_R03_23_GLO_DEF 
  </code></pre>
  
  <p>To</p>
  
  <pre><code>http://mynamespace/HL7/2X#ORU_R03_23_GLO_DEF 
  </code></pre>
  
  <p>However, whenever a message hits the port, it almost seems like the party is not being resolved because we receive an error as such</p>
  
  <pre><code>Error happened in body during parsing
  Error # 1
  
  Alternate Error Number: 301
  Alternate Error Description: Schema http://microsoft.com/HealthCare/HL7/2X#ORU_R03_23_GLO_DEF not found
  Alternate Encoding System: HL7-BTA
  </code></pre>
  
  <p>followed by another error:</p>
  
  <blockquote>
    <p>The Messaging engine failed to process a message submitted by
    adapter:MLLP Source URL:0.0.0.0:11001. Details:The published message
    could not be routed because no subscribers were found. This error
    occurs if the subscribing orchestration or send port has not been
    enlisted, or if some of the message properties necessary for
    subscription evaluation have not been promoted. Please use the Biztalk
    Administration console to troubleshoot this failure.</p>
  </blockquote>
  
  <p>The second error is somewhat expected based on the first, since no, there aren't ports subscribed to look for messages of type <code>http://microsoft.com/HealthCare/HL7/2X#ORU_R03_23_GLO_DEF</code> </p>
  
  <p>There are ports subscribed to <code>http://mynamespace/HL7/2X#ORU_R03_23_GLO_DEF</code> </p>
  
  <p>Is there anyway to check for sure if the Party is actually reading the incoming messages?</p>
  
  <p>Has anyone encountered this happening with BizTalk Parties? If so, how was it resolved?</p>