Batched EDI messages that are sent from the EdiSend pipeline are not saved for Health and Activity Tracking (HAT) in BizTalk Server 2006 R2

Article translations Article translations
Article ID: 961163 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario in BizTalk Server 2006 R2:
  • You use the EdiSend pipeline in a send port to send EDI messages.
  • You enable batching for the EDI party.

    Note For more information about how to do this, refer to the "MORE INFORMATION" section.
  • You enable the Message Bodies tracking option to track any messages after the ports are processed on the send port.
  • You open Health and Activity Tracking (HAT) to query the messages and then you select the Save all tracked messages option for the last Microsoft.BizTalk.Edi.DefaultPipelines.EdiSend event.
In this scenario, you find that the messages are saved as empty files.

RESOLUTION

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.

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:
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.

Prerequisites

You must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You do not have to restart your computer after you apply this hotfix. However, you have to restart the BizTalk Server service after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.biztalk.edi.batchinghelper.dll3.6.1508.287,94430-Jan-200915:32x86
Microsoft.biztalk.edi.batchmarkerpipelinecomponent.dll3.6.1508.255,20830-Jan-200915:32x86
Microsoft.biztalk.edi.ediintpipelines.dll3.6.1508.279,76030-Jan-200915:32x86
Microsoft.biztalk.edi.edipipelines.dll3.6.1508.255,17630-Jan-200915:32x86
Microsoft.biztalk.edi.messagecore.dll3.6.1508.2337,78430-Jan-200915:32x86
Microsoft.biztalk.edi.partneragreementmanager.dll3.6.1508.2411,55230-Jan-200915:32x86
Microsoft.biztalk.edi.pipelinecomponents.dll3.6.1508.2169,87230-Jan-200915:32x86
Microsoft.biztalk.ediint.pipelinecomponents.dll3.6.1508.2128,91230-Jan-200915:32x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

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

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
958296 FIX: An XML message remains in the active queue instead of in the suspended queue when you enable tracking after port processing for a send port that uses the EdiSend pipeline in BizTalk Server 2006 R2
For more information about how to batch outgoing EDI messages, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/dd801502.aspx
For more information about how to configure the X12 interchange batch creation settings to enable batching, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/dd770078.aspx
For more information about how to configure tracking for a send port, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/dd802250.aspx
For more information about software update terminology, 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

Properties

Article ID: 961163 - Last Review: July 15, 2009 - Revision: 1.1
APPLIES TO
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Branch Edition
Keywords: 
kbbtsmessaging kbbiztalk2006r2sp1fix kbsurveynew kbautohotfix kbexpertiseinter kbfix kbhotfixserver kbqfe KB961163

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com