SYMPTOMS
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.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft BizTalk Server 2004 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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
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.
|
| Btsmessageagent.dll | 3.0.6169.0 | 592,384 | 18-Nov-2005 | 03:16 |
| Btsmsgcore.dll | 3.0.6169.0 | 1,041,408 | 18-Nov-2005 | 03:16 |
| Microsoft.biztalk.interop.agent.dll | 3.0.6169.0 | 45,056 | 18-Nov-2005 | 02:37 |
| Microsoft.biztalk.messaging.dll | 3.0.6169.0 | 53,248 | 18-Nov-2005 | 02:46 |
| Microsoft.biztalk.streaming.dll | 3.0.6169.0 | 45,056 | 18-Nov-2005 | 02:37 |
| Microsoft.xlangs.biztalk.engine.dll | 3.0.6169.0 | 221,184 | 18-Nov-2005 | 02:50 |
| Microsoft.xlangs.engine.dll | 3.0.6169.0 | 221,184 | 18-Nov-2005 | 02:50 |
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.