FIX: Event ID 5799 and Event ID 5677 occur if you have a running orchestration that has a nil value in BizTalk Server 2006 or BizTalk Server 2006 R2

If you have a running orchestration that has a nil value in Microsoft BizTalk Server 2006 or in Microsoft BizTalk Server 2006 R2, and if the orchestration is passed to a non-nillable element on a Web service, the following error message is logged in the event log:

Event Type: Error
Event Source: BizTalk Server 2006
Event ID: 5799
Description:
The messaging engine was unable to resubmit a message for send port "Employer_Send_SOAP" with URL "http://xmlwsserver/Employer.asmx".
Details: "Cannot access a disposed object.
Object name: 'CEventingReadStream'.".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
In trace log
8578: 5799
[3]1278.25d0 05/24/2007-13:33:05.341 [errorhandler] ERROR:Sending error to eventlog: 'The messaging engine was unable to resubmit a message for send port "Employer_Send_SOAP" with URL "http://xmlwsserver/Employer.asmx".
Details: "Cannot access a disposed object.
Object name: 'CEventingReadStream'.". '
[3]1278.25D0::05/24/2007-13:33:05.341 [epmcoreengine] HandleResubmittedMsgs failed hr:80131622

Notes

• This is the expected error that should be thrown as an exception in the orchestration.
• This error occurs only if message body tracking is turned on.

The orchestration may stop processing when it shows an active status in the Group Hub in BizTalk Administration. The following event error may also be logged in the event log:

Event Type: Error
Event Source: BizTalk Server 2006
Event ID: 5677
Description:
The Messaging Engine encountered an error while suspending one or more messages. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Hotfix information

There are two versions of this hotfix:

• BizTalk Server 2006
• BizTalk Server 2006 R2

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.

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, submit a request to 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.

Prerequisites

You must have BizTalk Server 2006 installed to apply the BizTalk Server 2006 version of this hotfix. You must have BizTalk Server 2006 R2 installed to apply the BizTalk Server 2006 R2 version of this hotfix. hotfix.

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 item in Control Panel.

BizTalk Server 2006, x86 version

BizTalk Server 2006, x64 version

BizTalk Server 2006 R2, x86 version

BizTalk Server 2006 R2, x64 version

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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

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