08-09-05 10:53 PM
Hello.
Well, it looks like you have a subscription problem. What are you using as
your filer expression on the 2nd Orchestation? Make sure that property is
promoted on the sending message. You can see what’s promoted by viewing t
he
message contact in HAT on the suspended message. The items with Prompted =
True are routable to another orchestration. Sometimes, you have a very
limited number of items available.
I think an easier way to go would be to use the Start Orchestation (or Call
Orchestation) shape. Or Direct Binding using the Ports on Partner
Orchestation. Although, I have never had much luck getting get that to work
.
The best resource for more information on Binding Options is here:
http://geekswithblogs.net/cyoung/articles/19546.aspx
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
"Lakshmi Murthy" wrote:
> Hi,
>
> I have a requirement to transfer data between 2 orchestrations on the same
> machine. Hence, i opted for direct binding between both the orchestrations
.
> But, when i configure Send Port in my first orchestration as Direct Bindin
g
> choosing the option "Routing between ports will be defined by filter
> expressions on incoming messages in the MessageBox database"
>
> I am getting the following error in HAT:
>
> Uncaught exception terminated service
> CBITCEOrchestration_PRMsg.PROrchestration(688a6b44-be49-ea39-f701-b6c84fc3
236a), instance 4ef7790c-daa1-43db-9f02-9469ad51f49f
>
> Exception occurred when persisting state to the database.
>
> Exception type: PersistenceException
> Source: Microsoft.XLANGs.BizTalk.Engine
> Target Site: Void Commit()
> Help Link:
> Additional error information:
>
> A batch item failed persistence Item-ID a4695834-4a3c-4cf9-8e10-7ea1a721dd
6f
> 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. .
>
> Exception type: PersistenceItemException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
> 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.
>
> Exception type: PublishMessageException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
> Exception occurred when persisting state to the database.
>
> Exception type: PersistenceException
> Source: Microsoft.XLANGs.BizTalk.Engine
> Target Site: Void
> Commit(Microsoft.BizTalk.Agent.Interop.IBTMessageBatchEx[],
> Microsoft.XLANGs.Core.Segment,
> Microsoft.BizTalk.Agent.Interop.IBTOperationStatus ByRef)
> Help Link:
> Additional error information:
>
> A batch item failed persistence Item-ID a4695834-4a3c-4cf9-8e10-7ea1a721dd
6f
> 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. .
>
> Exception type: PersistenceItemException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
> 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.
>
> Exception type: PublishMessageException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
> and i can see the following error in Orchestration Debugger:
>
> The following error occurred when extracting sequence service information
> from the tracking DB: No information was found from this service instance
in
> the Tracking database. This can occur when orchestration tracking is not
> enabled, or because the TDDS service has not yet moved the data from the
> Message Box.
>
> I understand that this message is because not enabling tracking in
> orchestration.
>
> Please let me know how can i enable Tracking in Orchestration or how can i
> solve the above problem
>
> Thanks in advance
> Regards
> Lakshmi
[ Post a follow-up to this message ]
| 
