FIX: Error message when you try to save message bodies that are tracked by a PassThrough pipeline in BizTalk Server 2004: "Internal failure"

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
  • In Microsoft BizTalk Server 2004, you create an HTTP receive port that uses a custom pipeline. The custom pipeline contains only a MIME decoder.
  • You create a File send port that uses a PassThrough pipeline.
  • You use HTTP to submit a multiple part MIME message to the HTTP receive port in BizTalk Server 2004. The MIME message contains a message part and a payload part. Additionally, the MIME message is submitted by using a custom pipeline that contains a MIME encoder.
  • You try to save the message bodies that are tracked by the PassThrough pipeline in the Health and Activity Tracking (HAT) tool.
In this scenario, you receive an error message that is similar to the following in the HAT tool:
Internal Failure
When you view the tracked messages in the HAT tool, two saved messages appear as expected for the send pipeline. However, an "Internal Failure" error message is generated for the payload message part.

Additionally, the message file that is generated by the send port contains the body part. However, the message file does not contain the payload part. The ImgPart field is NULL in the Tracking_Part table for the payload part.

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.


You must have Microsoft BizTalk Server 2004 Service Pack 1 (SP1) installed to apply this hotfix.

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 tool in Control Panel.
File nameFile versionFile sizeDateTimeService pack requirement
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 more information about issues that can occur in BizTalk 2004 when a custom pipeline contains only a MIME decoder, click the following article number to view the article in the Microsoft Knowledge Base:
910912 FIX: The generated file contains two message body parts when you create a custom pipeline that contains only a MIME Decoder in BizTalk Server 2004
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
HAT msgbody internal failure MIME

Article ID: 909009 - Last Review: 01/17/2015 12:13:06 - Revision: 2.0

Microsoft BizTalk Server 2004 Standard Edition, Microsoft BizTalk Server 2004 Partner Edition, Microsoft BizTalk Server 2004 Enterprise Edition, Microsoft BizTalk Server 2004 Developer Edition

  • kbnosurvey kbarchive kbautohotfix kbbiztalk2004sp2fix kbbiztalk2004-2006swept kbbtshat kbbts kbbug kbfix kbhotfixserver kbqfe KB909009