- This topic has 1 reply, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘HIPAADecision.ProfessionalDecider(125e565a-a1cd-c6cb-d5e2-25eb93f502c1)’.
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: b1cb96e4-d31f-4355-b5fc-c8b55d153adc
Shape name: Send Claim to be batched
ShapeId: a9c6b952-a290-4a8f-9036-996873650baa
Exception thrown from: segment 1, progress 20
Inner exception: Exception occurred when persisting state to the database.
Exception type: PersistenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit()
The following is a stack trace that identifies the location where the exception occured
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.LongRunningTransaction.PendingCommit(Boolean ignore, XMessage msg)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, Context cxt, Segment seg, ActivityFlags flags)
at HIPAADecision.ProfessionalDecider.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Additional error information:
A batch item failed persistence Item-ID 79625df0-2754-4957-8a5c-991c58307f02 OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. .
Exception type: PersistenceItemException
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. with status -1061151998.
Exception type: PublishMessageException
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-
[quote user="Anonymous"]
A batch item failed persistence Item-ID 79625df0-2754-4957-8a5c-991c58307f02 OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. .
Exception type: PersistenceItemException
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. with status -1061151998.
Exception type: PublishMessageException
[/quote]
It’s a subscription error.
During the process, a message is sent to the MessageBox and if a subscriber is found the process can continue, if not there is an error.
To check why you don’t have the subscription :
- Go in the Administration console, BizTalk Group Page and set a New query
- Search for Subscriptions, in the result you can see the subscriptions and the expression of the subscription
- Check you message in error, in the property of the message, check the context to see the different value of the property.
- The value of the property in the message and in the expression of the subscription must match to work AND the property in the message must be promoted. Only promoted property can be used for routing.
Hope this help you.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.