PersistenceException after SP1

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I have 2 biztalk orchestrations that receive the below error seemingly
randomly. This error is documented in MS support article 814041, but
is supposedly fixed in SP1. We've also applied the hotfix from
KB895175, as it seemed related as well. The error is thrown from the
longrunningtransaction.commit method of a called orchestration upon
exiting that orchestration. The orchestration debugger will show that
it hasn't returned from the called orchestration, but the called
orchestration has completed (blue initialize at the end).

We're currently working with PSS, and it's been escalated to the
product team. I present this here asking if anyone has any ideas on
working around this - the problem happens deep into a long running
orchestration which correlates on incoming messages - and when this
exception is thrown, the service becomes suspended not resumable.
However, it continues subscribing to the correlation - thus pulling all
following messages into this abyss - instead of activating a new orch.
This is another bug if you ask me!

Uncaught exception terminated service
MyCompany.BizTalk.Orchestrations.PartRecordToERP(f8799bee-cfb4-e475-d904-4b322321eada),
instance 0bbecb4b-7760-41eb-8051-6ffa3cd9f764

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
54b88765-b964-4b92-80d6-0bb0c2f26402 OperationType MAIO_CommitBatch
Status -1061151992 ErrorInfo The operation could not be performed
because the message on which it was acting was not found in the
database. .

Exception type: PersistenceItemException
Source:
Target Site:
Help Link:
Additional error information:

A batch item failed persistence Item-ID
13e12e7e-233b-4166-ba86-bb9bf7cceb85 OperationType MAIO_SuspendMessage
Status -1061151992 ErrorInfo The operation could not be performed
because the message on which it was acting was not found in the
database. .

Exception type: PersistenceItemException
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
54b88765-b964-4b92-80d6-0bb0c2f26402 OperationType MAIO_CommitBatch
Status -1061151992 ErrorInfo The operation could not be performed
because the message on which it was acting was not found in the
database. .

Exception type: PersistenceItemException
Source:
Target Site:
Help Link:
Additional error information:

A batch item failed persistence Item-ID
13e12e7e-233b-4166-ba86-bb9bf7cceb85 OperationType MAIO_SuspendMessage
Status -1061151992 ErrorInfo The operation could not be performed
because the message on which it was acting was not found in the
database. .

Exception type: PersistenceItemException
Source:
Target Site:
Help Link:
Additional error information:



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

.



Relevant Pages

  • RE: System.OutOfMemoryException was thrown
    ... You are calling a stored procedure from an orchestration via the sql ... location using the Sql Adapter that will poll the database, ... Additional error information: ... Exception type: PersistenceItemException ...
    (microsoft.public.biztalk.general)
  • Deployment, side by side assemblies
    ... When I deploy a new version of a orchestration and set ... Additional error information: ... Exception type: TypeInitializationException ... assemblies with the same schema where only the assembly ...
    (microsoft.public.biztalk.general)
  • Re: System.OutOfMemoryException was thrown
    ... Receive Location configured with the Sql Adapter picks up messages that ... Send Port subscribes to the above messages and then Send Ports Send ... Logical Port in orchestration is then bound to physical MQ port end point. ... Exception type: PersistenceItemException ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk 2006 :: start orchestration wont start
    ... The orchestration starts by converting a flat file into an xml document, the document which causes an error contains a set of HEX 00's which, when converted to xml, causes an invalid failure error. ... Exception type: PersistenceItemException ...
    (microsoft.public.biztalk.general)
  • Re: Microsoft.XLANGs.Core.PersinstenceException
    ... This error is not coming from the orchestration. ... Exception occurred when persisting state to the database. ... Exception type: PersistenceItemException ... Exception type: PublishMessageException ...
    (microsoft.public.biztalk.general)