Consider the following scenario on a computer that is running Microsoft BizTalk Server 2006 R2, Microsoft BizTalk Server 2009 or Microsoft BizTalk Server 2010:
You use the AS2EdiReceive pipeline in a receive port to receive and to process Applicability Statement 2 (AS2) messages from your trading partners.
You enable the Failed Message Routing setting on the receive port.
You create a BizTalk party for the trading partner. Additionally, you configure the party to send a Message Disposition Notification (MDN) when the party is an AS2 message sender.
You receive an incoming AS2 message from the party that is not parsed correctly by electronic data interchange (EDI) pipeline components.
The AS2 message that is sent in Internet Information Services (IIS) is suspended.
In this scenario, the IIS worker process crashes. Therefore, the MDN is not sent to the sending party as expected. Additionally, an event is logged in the Application log, and another event is logged in the System log.
The event that is logged in the Application log resembles the following:
Event Type: Error Event Source: BizTalk Server 2006 EDI Event Category: None Event ID: 8114 Description: Error encountered during parsing. The X12 transaction set with id '<id>' contained in functional group with id '1', in interchange with id '000000025', with sender id 'THEM ', receiver id 'US ' is being suspended with following errors: Error: 1 (Field level error) SegmentID: PO1 Position in TS: 8 Data Element ID: PO108 Position in Segment: 8 Data Value: 4 4: Data element too short
The event that is logged in the System log resembles the following:
Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 1009 Description: A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '<process id>'. The process exit code was '0x0'.
Note: If you use BizTalk Server 2009 or BizTalk Server 2010, the Event Source and Event Category in above events are “BizTalk Server 2009” or “BizTalk Server 2010”.
This issue occurs because the BTSHttpRecieve.dll assembly passes an invalid context to IIS. The invalid context causes an access violation in the IIS worker process. Therefore, the IIS worker process crashes.
Cumulative update information
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:
2497789 Cumulative update package 1 for BizTalk 2010
Cumulative update informationThe hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.
For more informationabout how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2497794 Cumulative update package 2 for BizTalk Server 2009
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.
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.
You must have BizTalk Server 2006 R2 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk Server host instance after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace other hotfixes.
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.
To work around this issue, disable the Failed Message Routing setting on the receive port.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to create a solution that receives EDI messages over AS2 transport and then returns MDNs, visit the following Microsoft Developer Network (MSDN) Web sites: