Symptoms

Consider the following scenario in a Microsoft BizTalk Server environment:

  • You create a send port that uses the AS2EDISend Pipeline component or the AS2Send Pipeline component to send Applicability Statement 2 (AS2) messages.

  • You select the Track Message Bodies - Request message after port processing check box to save and track message content after the message is sent on the send port.

In this scenario, the AS2 send instances remain active even after the messages are processed.

Resolution

Cumulative update information

For BizTalk Server 2009

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for BizTalk Server 2009, click the following article number to view the article in the Microsoft Knowledge Base:

2557149 Cumulative update package 3 for BizTalk Server 2009

For BizTalk Server 2010

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2010.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2573000 Cumulative update package 2 for BizTalk Server 2010

Workaround

To work around this problem temporarily if you cannot apply this fix, disable tracking after port processing for the send port, and then use Electronic Data Interchange (EDI) Status Reporting instead.

To disable tracking after port processing, follow these steps:

  1. Click Start, click Programs, click Microsoft BizTalk Server 2009, and then click BizTalk Server Administration.

  2. In the console tree, expand the BizTalk group and the BizTalk application for which you want to disable tracking for a send port.

  3. Click Send Ports, right-click the send port, click Properties, and then click Tracking.

  4. Click to clear the Track Message Bodies - Request message after port processing check box.

For more information about how to enable BizTalk EDI/AS2 Runtime Status Reporting, visit the following Microsoft TechNet website:

Configuring EDI/AS2 Runtime Using the Configuration Manager

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 about how to configure various tracking options during run time for orchestrations, send ports, receive ports, and pipelines by using the BizTalk Server Administration Console, visit the following Microsoft Developer Network (MSDN) website:

Configuring Tracking Using the BizTalk Server Administration ConsoleFor more information about what actions occur as a message is processed, visit the following Microsoft TechNet website:

Service Instance StatesFor more information about how the AS2 components in BizTalk Server 2010 process outgoing AS2 messages, visit the following Microsoft Developer Network (MSDN) website:

How BizTalk Server Sends AS2 MessagesFor more information about the tracking type options for a logical endpoint, visit the following Microsoft TechNet website:

TrackingTypes EnumerationFor more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk Server hotfixes

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×