Article ID: 929737 - Last Review: November 15, 2007 - Revision: 1.2 Error message when you submit an MTS05 message that does not contain a SWIFT body part in BizTalk Server 2006: "There is no body part in the InterChange"
On This PageSYMPTOMSConsider the following scenario:
Error message 1 Event ID 5753
Event Type: Error Event Source: BizTalk Server 2006 Event Category: BizTalk Server 2006 Event ID: 5753 Description: A message received by adapter "FILE" on receive location "ReceiveLocation1" with URI "C:\temp\FileIn\*.*" is suspended. Error details: There was a failure executing the receive pipeline: "NRISwiftPipelines.BatchReceivePipeline, NRISwiftPipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a7e4379d7fc7e441" Source: "SWIFT Disassembler" Receive Port: "ReceivePort1" URI: "C:\temp\FileIn\*.*" Reason: There is no body part in the InterChange. MessageId: {A450F849-EDBD-4822-BA8F-B92743F54DCE} InstanceID: {9592B013-5233-4DC9-A87C-66E925BC303F} Error message 2 Event ID 5719
Event Type: Error Event Source: BizTalk Server 2006 Event Category: BizTalk Server 2006 Event ID: 5719 Description: There was a failure executing the receive pipeline: "NRISwiftPipelines.BatchReceivePipeline, NRISwiftPipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a7e4379d7fc7e441" Source: "SWIFT Disassembler" Receive Port: "ReceivePort1" URI: "C:\temp\FileIn\*.*" Reason: There is no body part in the InterChange. MessageId: {A450F849-EDBD-4822-BA8F-B92743F54DCE} InstanceID: {9592B013-5233-4DC9-A87C-66E925BC303F} Error message 3 Event ID 4099
Event Type: Error Event Source: BizTalk Accelerator for SWIFT Event Category: None Event ID: 4099 Description: Error during application execution. The error message is: There is no body part in the InterChange. CAUSEThis problem occurs because of an issue that is related to the check of
missing body schema. Based on the MTS05 schema in Category 0, a message
without a body part or a trailer part should be allowed in BizTalk Server 2006.
In this scenario, when the pipeline tries to parse the message that does
not contain the body part, the parse cannot be successful. This behavior occurs because of a problem
in the original BizTalk Accelerator for SWIFT 2006 Message Pack. RESOLUTIONHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.PrerequisitesYou must have BizTalk Accelerator for SWIFT 2.3 installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. APPLIES TO
| Article Translations
|
Back to the top
