FIX: Error message when you use the BizTalk Adapter for SQL Server to process multipart messages: "Uncaught exception"

This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft BizTalk Server 2006, you receive an error message that resembles the following error message when you process multipart messages by using the Microsoft BizTalk Adapter for Microsoft SQL Server:
Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'BizTalkSqlTest.odxSQL_TEST(03beb95c-038c-2009-4677-0e435d5421e1)'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: da7cc109-4d60-4944-a584-490539b68c8f
Shape name: Receive_2
ShapeId: 83f95b82-f56f-436e-a8b4-942433cc1921
Exception thrown from: segment 1, progress 10
Inner exception: Multi-part message 'msgSQL_TEST_Rsp' has body part 'BodyPart5', expected body part 'BodyPart1'.

Exception type: WrongBodyPartException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void ReadMessageState(Microsoft.XLANGs.Core.Envelope, Microsoft.XLANGs.BaseTypes.XLANGMessage)

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.


No prerequisites are required.

Restart requirement

You do not have to 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 item in Control Panel.
File nameFile versionFile sizeDateTime
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
To work around this issue, do not include multiple records in the message that you send to the BizTalk Adapter for SQL Server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more 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

Article ID: 918316 - Last Review: 01/17/2015 14:27:27 - Revision: 2.0

Microsoft BizTalk Adapter for SQL

  • kbnosurvey kbarchive kbautohotfix kbbiztalk2006presp1fix kbbtsadapters kbbts kbbug kbfix kbHotfixServer kbqfe KB918316