I am not sure how many times I have come across this error. I finally had a few moments to actually troubleshoot this error.
The reason for this message is that the orchestration is expecting as the first message part being the MSH segment, whereas it actually finds the BodySegments component. The orchestration then attempts to pick up the message, which is where it errors.
The key to getting this issue resolved is the order that you create the multi-part message.
I know I have made this mistake multiple times, I create the multi-part message type, and renamed the MessagePart_1 to BodySegments, since the IsBodyPart property was already set to true, I then would create the MSHSegment and ZSegments.
This would cause me headaches because the orchestration picking up the message would create the error.
Looking at the code, you have to create the message parts in the correct order. In the Type window, you see the parts in alphabetical order.
However, behind the scenes, it remembers the order that it was created. I have the following excerpt of the odx that shows what is going on behind the scenes: The ADT_A02Type is correct, whereas the ADT_A03Type is incorrect.
So make sure that you create the parts in the correct order and you will not have a problem. If they are created in the wrong order, the only solution I have used is to delete the multi-part message and recreate it again.
By the way, this is only an issue on message that are inbound, outbound messages, the pipeline component is intelligent enought to put things together (even if they are defined in the wrong order), it is the orchestration that consumes the message that is finicky.
posted @ Tuesday, August 15, 2006 12:00 PM