Microsoft KB Archive/895175

= FIX: An orchestration is not completed successfully, and an exception is logged in an atomic transaction in BizTalk Server 2004 SP1 =

Article ID: 895175

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Service Pack 1

-





SYMPTOMS
You may experience the following problem in Microsoft BizTalk Server 2004 Service Pack 1 (SP1). When you try to run an orchestration that contains messages that are declared in a Scope shape where the Transaction Type property is set to Atomic, the orchestration is not completed successfully. This problem occurs when BizTalk Server 2004 tries to persist the messages to the database.

Additionally, an exception that is similar to the following is logged in an atomic transaction in Microsoft BizTalk Health and Activity Tracking (HAT): Microsoft.XLANGs.Core.PersistenceException: Exception occurred when persisting state to the database. ---> Microsoft.BizTalk.XLANGs.BTXEngine.PersistenceItemException: A batch item failed persistence Item-ID 4a3bbe04-691d-4eea-b0b9-baa2b7ab9de9 OperationType MAIO_CommitBatch Status -1061151960 ErrorInfo Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database. . ---> 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 Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database. with status -1061151960. ---> Microsoft.XLANGs.Core.PersistenceException: Exception occurred when persisting state to the database. ---> Microsoft.BizTalk.XLANGs.BTXEngine.PersistenceItemException: A batch item failed persistence Item-ID 4a3bbe04-691d-4eea-b0b9-baa2b7ab9de9 OperationType MAIO_CommitBatch Status -1061151960 ErrorInfo Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database. . ---> 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 Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database. with status -1061151960. ---> Microsoft.XLANGs.RuntimeTypes.RuntimeInternalErrorException at Microsoft.BizTalk.XLANGs.BTXEngine.BTXService.ReleasePartsUnderConstruction  at Microsoft.BizTalk.XLANGs.BTXEngine.CommitHelper.Commit(BTXSession session, ITransaction transaction, Object[] batches, IBTOperationStatus& s) at Microsoft.BizTalk.XLANGs.BTXEngine.CommitManager.Commit(IBTMessageBatchEx[] batches, Segment seg, IBTOperationStatus& s)   --- End of inner exception stack trace ---   --- 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.TransactionalContext.OnCommit   at Microsoft.XLANGs.Core.AtomicTransaction.OnCommit   at StatuFac.StatutFacturation.segment16(StopConditions stopOn) in c:\Documents and Settings\nnn\Local Settings\Temp\1\4wow7d17.18.cs:line 14677   at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp) Microsoft.XLANGs.Core.PersistenceException Scoped@ Notes
 * In this information,  is a placeholder for information that is specific to your orchestration.
 * This problem does not occur in BizTalk Server 2004 when BizTalk Server 2004 Service Pack 1 has not been applied.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
This hotfix requires BizTalk Server 2004 Service Pack 1.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name --  04-Mar-2005  02:11  3.0.6109.0        221,184  Microsoft.xlangs.biztalk.engine.dll 04-Mar-2005 02:11  3.0.6109.0        217,088  Microsoft.xlangs.engine.dll



WORKAROUND
To work around this problem, remove any messages that are declared in the Scope shape where the Transaction Type property is set to Atomic. Instead, declare the messages in the enclosing scope.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: BTS2004 EBizSE 1569

Keywords: kbbiztalk2004-2006swept kbbiztalk2004presp2fix kbbug kbfix kbprb kbhotfixserver kbqfe KB895175

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.