|
Home > Archive > BizTalk Server General > March 2006 > Microsoft.XLANGs.Core.PersinstenceException
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Microsoft.XLANGs.Core.PersinstenceException
|
|
|
| Hi,
I'm getting a strange BizTalk error above.
Within the error message it states that "The published message could
not be routed because no subscribers were found."
The error message appears for the orchestration that is bound to a
receive location that uses DefaultPipelins.XMLReceive.
The orchestration is a "wrapper" orchestration with a receive shape and
a send shape and a receive port bound to a receive location and a
direct send port.
I have another one of these "wrapper" orchestrations bound to a receive
location.
Both locations receive the same kind of message (schema) from the same
application. Both have direct send ports.
One works, the other one doesn't and throws the error above.
I've deployed, undeployed, re-deployed, re-started the host. None of
that did anything.
In BTS subscription viewer the orchestration has an "Activate".
Help!
Ana
Full Error Message Follows:
---------------------------------------
Uncaught exception terminated service
Orch1.Wrapper1(2a5a2e57-162e-5693-3c6b-f7eb7cee63ac), instance
6a619be1-f50a-4362-9e61-25a65afbd0db
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
0b913b4e-b877-46e8-aa98-21d7b5198489 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
0b913b4e-b877-46e8-aa98-21d7b5198489 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:
For more information, see Help and Support Center at
| |
| Greg Forsythe 2006-03-07, 8:47 pm |
| This error is not coming from the orchestration.
The error is generated when the incoming message is published to the
MessageBox and the MessageBox cannot find either an orchestration or send
port that subscribes to this message.
You need to check the subscription information for your orchestration and
match it against the message context of the failing message.
You can use the BTSSubscriptionViewer.exe application in the SDK/Utilities
folder to view the current subscriptions.
Make sure the appropriate message context properties are Promoted.
Greg
"AnaB" <anabanana.discussions@yahoo.com> wrote in message
news:1141771966.469903.103640@i40g2000cwc.googlegroups.com...
> Hi,
> I'm getting a strange BizTalk error above.
>
> Within the error message it states that "The published message could
> not be routed because no subscribers were found."
>
> The error message appears for the orchestration that is bound to a
> receive location that uses DefaultPipelins.XMLReceive.
>
> The orchestration is a "wrapper" orchestration with a receive shape and
> a send shape and a receive port bound to a receive location and a
> direct send port.
>
> I have another one of these "wrapper" orchestrations bound to a receive
> location.
>
> Both locations receive the same kind of message (schema) from the same
> application. Both have direct send ports.
>
> One works, the other one doesn't and throws the error above.
>
> I've deployed, undeployed, re-deployed, re-started the host. None of
> that did anything.
>
> In BTS subscription viewer the orchestration has an "Activate".
>
> Help!
>
> Ana
>
> Full Error Message Follows:
> ---------------------------------------
> Uncaught exception terminated service
> Orch1.Wrapper1(2a5a2e57-162e-5693-3c6b-f7eb7cee63ac), instance
> 6a619be1-f50a-4362-9e61-25a65afbd0db
>
> 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
> 0b913b4e-b877-46e8-aa98-21d7b5198489 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
> 0b913b4e-b877-46e8-aa98-21d7b5198489 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:
>
>
>
> For more information, see Help and Support Center at
>
| |
|
| Hi, Greg,
What am I looking for in the BTSSubscriptionViewer?
Like I mentioned, looking at the orchestration I can see two
properties: ReceivePortID and MessageType - same properties as I see
for the other wrapper orchestration that's working.
There are no send ports to check, because this orchestration has a
direct binding port to another orchestration.
Do I now need to look at the message to make sure that those two
properties are promoted on it? Why wouldn't they be? How do I check?
Thanks.
Ana
| |
|
| Also, when I look in HAT, Under "Suspended Messages". For my
orchestration that's not working, the message type is empty.
Does this mean, that the MessageType property is not being promoted?
Why would this happen?
Ana
| |
|
| Hi, again,
I have tested the orchestration with a BizTalk Schema "generated"
instance of the message. It resulted in the same error.
I also got about 200 e-mails from my WMI suspended queue listner about
it. I'm not sure why I get so many instead of one.
I can see that there is a subscription associated with my orchestration
in the BTSSubscriptionViewer.
Help please!
I'm out of ideas.
Ana
| |
| Greg Forsythe 2006-03-08, 5:53 pm |
| There are two possible scenarios here.
1. The message being published by the receive port has no subscriber
2. The message being published by the wrapper orchestration has no
subscriber.
The Routing Failure Report that is suspended has no content but does have
the complete message context. It is the message context that is used for
routing so this is all that is required.
If the problem is at step 1 then:
The Wrapper Orchestration is bound to a port and I assume has no additional
filters set on the receive shape in the orchestration.
So its Subcription will be on ReceivePortID and MessageType.
Are these properties present and promoted in the message context of the
Routing Failure Report.
The ReceivePortID should always be present. The MessageType will only be
present is a Disassembler component in the pipeline has been able to
recognize the message and promote the MessageType property. If you are using
the PassThru pipeline the MessageType will not be set.
If the problem is at step 2.
There should be a property in the message context called
SendingOrchestrationID with a guid, but it won't be promoted
You need to find the subscription properties on the orchestration and match
with the message context.
In the message context the property must contain the correct value AND be
promoted.
If the problem is at step 2 I will need to know the subscription properties
and the values in the message context.
Greg
"AnaB" <anabanana.discussions@yahoo.com> wrote in message
news:1141828259.152877.59510@p10g2000cwp.googlegroups.com...
> Hi, Greg,
> What am I looking for in the BTSSubscriptionViewer?
> Like I mentioned, looking at the orchestration I can see two
> properties: ReceivePortID and MessageType - same properties as I see
> for the other wrapper orchestration that's working.
> There are no send ports to check, because this orchestration has a
> direct binding port to another orchestration.
> Do I now need to look at the message to make sure that those two
> properties are promoted on it? Why wouldn't they be? How do I check?
> Thanks.
> Ana
>
|
|
|
|
|