Hi Everyone,

Currently working on some BizTalk orchestrations.

But I can't get it to work.

Without an orchestration I am able to send message from my reveiceports through my send ports. The send is then configured with a filter expression (in the biztalk administration console).
When I use an Orchestration between my receive and sendport I got an error message saying that the message (biztalk) found no active subscriptions.
Before I implemented the orchestration I deleted the filterexpression on the send port, because in the orchestration I am pointing (using binding in the biztalk administration) to the right send port.

Now I still get the message that there are no subscriptions found and my message keeping getting suspended. What am I doing wrong?

Is a filter expression on the sendport mandatory when using an orchestration? (would be strange)
I am using BizTalk 2010.
Also important to tell is that I have no properties promoted because every message needs to be transformed.

Does someone know why my messages are not accepted? Or can someone help me in the right direction?

I already done the following things. 

Checked if all are in the enlisted state
Checked if the XML receive pipeline is activated

It is clear that the issue comes from receive pipeline

Try to check receive pipeline is pointing to XML receive and besides that you can see dots..click on it and set AllowUnRecognized messages to True

The error is because your Orchestration is unable to subscribe to the input message. Check if the xml that you are receiving in the receive port and the xsd that you have in orchestration have the same MessageType.

Hi,

As per your explanation, I believe you have binded your physical receive port with the orchestration logical port. In this case, you need to select the receive pipeline as XMLReceive because it promotes the necessary properties (most importantly MessageType) which are required by an orchestration to subscribe to a message.

Also, when you have removed the orchestration, you need to apply a filter on send port in order to make a subscription of the message coming from receive port.

In case, you have not applied any map on send port, you can just apply the Receive Port Name filter on the send port with PassThrough pipeline on the receive port. But, if you have applied a map on the send port, you need to use the XmlReceive pipeline on the receive port in order to promote the MessageType property.

Hope this will help.

Thanks,

Sumit

Hi Tiron,

Above replies are the most likely reason , adding more to it.

1.Did you restart your host instance after making the change and deploying. 

2.Also please check the first receive shape of Orchestration as to which message its associated with.

3.You can also look into the subscription table to find the subscribers.

Hi
Please go thru the following steps as I am not sure about your Biztalk comfort level

1. First make sure you that you see your deployed schema in the Biztalk application,
    You can see this via BTS Admin console-> Your application -> schemas
    Your schema SHOULD be there.. if not you have to deploy that again. There should be ONLY one schema for given Message Type.
2. Restart the Host instance
3. Now if you encounter routing failure again, then open failed message, exploit it.
    Verify that for which message type failure message is generated. Biztalk wraps the failure message around the original message.
4. Acknowledgements also play important role in such cases. please verify that whether received message is not asking for ack.

   

Hi Everyone,

I started over with my project and now everything works. 
My orchestration is now picking up the message. Unfortunatly I cannot say why it didn't worked the first time.

But now when I included a transformation shape I get the follow error which is not telling me anything.

Does some know what is going on?
The only thing that I see it this. 
I want the orchestration to transform my RequestMessage to my TransformedMessage. But somehow the send shape is giving me this error.

 

xlang/s engine event log entry: Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'BizTalkServerProject1.Orchestration(f818502d-214d-3f41-1c26-a95e32dcb960)'.
The service instance will remain suspended until administratively resumed or terminated. 
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: 51400fa5-54ae-4434-b5f7-082e68a60ddf
Shape name: SendCustomerMessage
ShapeId: a22f02ef-3fbb-4a13-bd06-e24bf13d5cba
Exception thrown from: segment 1, progress 13
Inner exception: Failed while attempting to send message 'RequestMessage'.
        
Exception type: SendFailedException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void WriteMessageState(Microsoft.BizTalk.Interop.IBTPEPInfoLookup, System.Guid, Microsoft.XLANGs.BaseTypes.XLANGMessage, Microsoft.XLANGs.Core.Segment, System.String, System.String, System.Collections.IList, Boolean, System.Collections.IList)
The following is a stack trace that identifies the location where the exception occured

   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.WriteMessageState(IBTPEPInfoLookup pepLookup, Guid portId, XLANGMessage msg, Segment seg, String opname, String url, IList promoteProps, Boolean track, IList toPromote)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXLogicalPortBinding.SendMessage(XLANGMessage msg, XlangStore store, Segment seg, OperationInfo op, IList additionalProps, IList toPromote, Boolean ignoreRoutingFailure)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, Context cxt, Segment seg, ActivityFlags flags)
   at BizTalkServerProject1.Orchestration.segment1(StopConditions stopOn)
   at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Additional error information:

        Exception from HRESULT: 0xC0C01672
        
Exception type: COMException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void PostToSendPort(System.Guid ByRef, Microsoft.BizTalk.Agent.Interop.IBTMessageBatch, Microsoft.BizTalk.Agent.Interop.IBTMessage, System.String, System.String, Microsoft.BizTalk.Interop.IBTMMessageList ByRef)
The following is a stack trace that identifies the location where the exception occured

   at Microsoft.BizTalk.Interop.IBTPEPInfoLookup.PostToSendPort(Guid& sendPortID, IBTMessageBatch batch, IBTMessage msg, String operationName, String url, IBTMMessageList& dlMsgList)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.WriteMessageState(IBTPEPInfoLookup pepLookup, Guid portId, XLANGMessage msg, Segment seg, String opname, String url, IList promoteProps, Boolean track, IList toPromote)

        

Well I also managed to get that out of the way. For some reason a restart did the job. Thanks for helping everyone. 

@tiron_66: As you mentioned it's resolved now, so please close the thread.