Microsoft KB Archive/941261

= FIX: Event ID 5720 is logged when you specify the BTAHL72XPipeline pipeline in a send port in BizTalk Server 2006 R2 =

Article ID: 941261

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 R2 Standard Edition
 * Microsoft BizTalk Server 2006 R2 Developer Edition
 * Microsoft BizTalk Server 2006 R2 Enterprise Edition
 * Microsoft BizTalk Server 2006 R2 Branch Edition

-



SYMPTOMS
In Microsoft BizTalk Server 2006 R2, you specify the BTAHL72XPipeline pipeline in a send port. When you send a message by using the send port, an event that resembles the following is logged in the Application log: Event Type: Error

Event Source: BizTalk Server 2006

Event Category: BizTalk Server 2006

Event ID: 5720

Date:

Time:

User: N/A

Computer:

Description:

There was a failure executing the send pipeline: &quot;BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=1.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35&quot; Source: &quot;BTAHL7 2.X Assembler&quot; Send Port: &quot;HL7_SP&quot; URI: &quot;C:\Labs\HL7_Outbound\%MessageID%.txt&quot; Reason: Specified cast is not valid.



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

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.

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 &quot;Applies to&quot; section.



MORE INFORMATION
After you apply this hotfix, set the MessageEncoding property of a message before you send the message to the BTAHL72XPipeline pipeline. For example, set the MessageEncoding property by using the following code. DoorbellFinalMessage(BTAHL7Schemas.MessageEncoding)=65001 If you do not set the MessageEncoding property after you apply this hotfix, an event that resembles the following is logged: Event Type: Error

Event Source: BizTalk Server 2006

Event Category: BizTalk Server 2006

Event ID: 5720

Date:

Time:

User: N/A

Computer:

Description:

There was a failure executing the send pipeline: &quot;BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=1.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35&quot; Source: &quot;BTAHL7 2.X Assembler&quot; Send Port: &quot;MLLPSendPort&quot; URI: &quot;localhost:11000&quot; Reason: Object reference not set to an instance of an object.

This event differs from the event that is mentioned in the &quot;Symptoms&quot; section.

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

Keywords: kbexpertiseadvanced kbfix kbpubtypekc kbqfe kbhotfixserver KB941261

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.