And this error message is followed by another error message like this:
When you carefully read the error message, it is saying there is an orchestration that has not been enlisted whether to receive port or send port. And when you check your application you just deployed through BizTalk Administration Console you find that all orchestration has been enlisted into both send port and receive port.
What is the Root Cause???
One of the most possibility reason is because you have exactly root name or node name in one of your schema in your BizTalk solution.
But when you check on your schema, you did not find any similar schema root name between one and another and that sounds weird doesn't it?
Especially in my case, I only have two schemas and I am totally giving the different for both of my schemas like these pictures below
Apparently I realised that I have another BizTalk solution deployed long before I deployed my recent solution and I found out that I had the schema root name exactly similar with the one I just created. The point is that I have similar schema root name in different BizTalk Solution
If you look the picture below, it has different solution but with the same root name with the previous picture above
What's the Solution then?
As been mentioned in many blogs explaining about this error, what you need to do is just change one of your schema root name and based on the problem I faced, I finally knew that you cannot give the same schema root name in your BizTalk application as long as you deploy into the same BizTalk Server (even though you deploy into different BizTalk Application you create in BizTalk Administration Console) and That will be it. When you re-deploy your solution it should be working as you expected.
Well, hope this can help you out with the same problem
And happy trying :D
