FIX: An "Index was outside the bounds of the array" error message is logged and existing messages do not correctly correlate after you install BizTalk Server 2004 Service Pack 1

Consider the following scenario. You have orchestrations that contain long-running transactions, and the transactions are correlated. Then, you install Microsoft BizTalk Server 2004 Service Pack 1 (SP1). After you install the service pack, existing messages do not correctly correlate, and an error message that is similar to the following is logged in the Application log:

Event Type: Error
Event Source: FatalBrokerException
Event Category: None
Event ID: 0
Description: <FatalBrokerException><CorrelatedField>xxx</CorrelatedField><Version>1</Version><Message>Index was outside the bounds of the array.</Message><Source>Microsoft.XLANGs.BizTalk.Engine</Source><Stack> at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase._flowPropertiesFrom(XLANGMessage msg, Int32 iOperation) at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.ReceiveMessage(Int32 iOperation, Envelope env, XLANGMessage msg, Correlation[] initCorrelations, Context cxt, Segment s) at TestBroker.TestBrokerOrchestration.segment2(StopConditions stopOn) at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception&amp; exp)</Stack></FatalBrokerException>

Note New messages do not experience this problem. New messages correctly correlate.

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Warning You cannot roll back this hotfix from the BizTalk Server environment. Therefore, make sure that you fully test this hotfix in a test environment before you apply this hotfix to a production environment. Do not try to use Add or Remove Programs to remove this hotfix because this does not roll back the database changes, and leaves the BizTalk Server environment in an inconsistent state.

Prerequisites

To apply this hotfix, you must have BizTalk Server 2004 Service Pack 1 (SP1) installed on the computer.

Restart requirement

You must restart the 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.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base: