Error Connecting two orchestrations- Can anyone help

Is your direct binding working?

I’m guessing the problem is in your direct binding. Make sure you have an active subscription for the message or you’ll get that error.

[quote user="Anonymous"]Hi,

I am trying to call another orchestration within an orchestration using the Call Orchestration tool.

Ex. orchestration1 will call orchestration2

orchestration1 is has a \"parallelAction\" to activate two actions:
[b:9624c72344]action one[/b:9624c72344]: to send an xml message to another orchestration (orchestration3, say) using the Direct Binding mechanism.
[b:9624c72344]action two[/b:9624c72344]: to call another orchestration (orchestration2)

orchestration2 is going to do a mapping to a database to save a certain record.

When I tried to test it I got this long error:

Microsoft.XLANGs.Core.PersistenceException: Exception occurred when persisting state to the database. —> Microsoft.BizTalk.XLANGs.BTXEngine.PersistenceItemException: A batch item failed persistence Item-ID 8fc8316d-7285-4bdf-ba2f-5119895bea63 OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. . —> Microsoft.BizTalk.XLANGs.BTXEngine.PublishMessageException: Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message. The error was The published message could not be routed because no subscribers were found. Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. with status -1061151998. —> Microsoft.XLANGs.Core.PersistenceException: Exception occurred when persisting state to the database. —> Microsoft.BizTalk.XLANGs.BTXEngine.PersistenceItemException: A batch item failed persistence Item-ID 8fc8316d-7285-4bdf-ba2f-5119895bea63 OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. . —> Microsoft.BizTalk.XLANGs.BTXEngine.PublishMessageException: Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message. The error was The published message could not be routed because no subscribers were found. Please use the Health and Activity Monitoring (HAT) tool to diagnose this situation. with status -1061151998.
— End of inner exception stack trace —
— End of inner exception stack trace —
at Microsoft.BizTalk.XLANGs.BTXEngine.CommitManager.Commit(IBTMessageBatchEx[] batches, Segment seg, IBTOperationStatus& s)
at Microsoft.BizTalk.XLANGs.BTXEngine.TransactionBatch.Commit(IBTMessageBatchEx[] batches, ITransaction transaction, IBTOperationStatus& s)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
— End of inner exception stack trace —
— End of inner exception stack trace —
— End of inner exception stack trace —
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean terminate)
at Microsoft.XLANGs.Core.ServiceContext.PendingCommit(Boolean ignore, XMessage msg)
at Microsoft.XLANGs.Core.ExceptionHandlingContext.PendingCommit(Boolean ignoreCommit, XMessage msg)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, Context cxt, Segment seg, ActivityFlags flags)
at SamplePartnerPorts.Orchestration1.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Microsoft.XLANGs.Core.PersistenceException

[b:9624c72344]Can anyone help? I will really appreciate it.[/b:9624c72344][/quote]

If you're running BizTalk Server 2004 with SP1 (N.B. not SP2 ! ), applying hotfix KB895175 might help you out.