I am having an issue with an orchestration that I am creating that has the following parameters.

I receive a message (XML) on a Request/Response port. The message is then sent to a send port that passes the message to the MSMQT. The MSMQT passes the message to an application. After the app does its processing, it passes a Response XML file back to a different MSMQ queue (part of the architecture unfortunately). A receive port listening in on the second MSMQT takes the message, passes the message to the Response part of the port operation.

I set the first receive message initializes the BTS.MessageID as the correlation set property. The remaining messages use that correlation set. The issue is that when I build the solution, I get the following error:

"in a sequential convoy the ports must be identical."

I researched this issue and found that this issue occurs when you do not share a receive port.

I was wondering if anyone has encountered this problem and found a way around it. I have to stay with the 2 receive port system. Would separating the orchestration into two work? I should be able to use the BTS.MEssageID property in that second orchestration.

Any help would be greatly appreciated on this issue.

I have encountered a similar problem. Have you found any resolution?

It's just happening because you are initializing and following a correlation both in a receive shape. Try to initialize the correlation in a send shape and then follow the correlation using a receive shape.

I Hope it helps !

Bruno Spinelli.

Hello Bruno,
I am also having the same issue. The requirement is such, that i have to use one receive port scheduled message in order to activate the orchestration & two another receive port for same message type.

As you said, try to initialize the correlation in a send shape and then follow the correlation using a receive shape.
My question is:which send shape & which receive shape you are talking about?

Please reply... thanks alot in advance
Regards,
harry

Happy Programming,
harry

In BizTalk server try to add one more orchestration that will pick the xml file and transform it to a text file for another position and keep your solution simple and loosely coupled, You can modify any component without splitting or ending the whole message flow.

http://www.athenainfotech.co.uk/free...k-health-check