Microsoft KB Archive/935347

= FIX: Characters appear as question marks after you handle an input message that contains ISO 8859/1 characters when you use the Microsoft BizTalk Accelerator for HL7 1.3 =

Article ID: 935347

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 Standard Edition
 * Microsoft BizTalk Accelerator for HL7 1.0 Enterprise Edition

-





SYMPTOMS
When you handle an input message on a BizTalk Server 2006 computer by using the Microsoft BizTalk Accelerator for HL7 1.3, ISO 8859/1, characters in the input message appear as question marks (?). For example, you send a message that includes the following ISO 8859/1 string: öäåüÖÄÅÜTestString After the BizTalk Accelerator for HL7 1.3 disassembler (DASM) processes the message, the string resembles the following string: ????????TestString If a map is specified in the receive port or in the send port, you may also receive the following error message: Event Type: Error

Event Source: BizTalk Server 2006

Event Category: BizTalk Server 2006

Event ID: 5784

Date: 6/7/2007

Time: 3:49:42 PM

User: N/A

Computer: ComputerName

Description:

The Messaging Engine failed while executing the inbound map for the message coming from source URL:&quot;C:\Labs\HL7_Inbound\*.txt&quot; with the Message Type &quot;MessageType&quot;. Details:&quot;'Unicode (UTF-8)' is not a supported encoding name. Parameter name: name&quot;



CAUSE
This issue occurs because the BizTalk Accelerator for HL7 2.X receive pipeline only supports ASCII encoding. The receive pipeline does not support an ASCII character set if the ASCII character values are larger than 127. Therefore, some characters in the input message are replaced by question marks (?).



RESOLUTION
To resolve this problem, deploy a custom pipeline that has the encoding property set to Western European encoding. Before you build a new custom pipeline, you must install hotfix 935347. For more information about how to build the custom pipeline, see the &quot;More information&quot; section.

Hotfix information
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
You must have the BizTalk Accelerator for HL7 1.3 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 item in Control Panel.



MORE INFORMATION
After you install this hotfix, the BTAHL7 2.X receive pipeline supports the following encoding sets:
 * Western European
 * ASCII
 * UTF8

If a user selects an encoding other than ASCII, UTF8, or Western European, the following error message and information appear when the user tries to parse the message:

Input encoding is not supported.

Supported encodings are - ASCII, UTF8, Western European.

Western European encoding supports all European characters. If an input message contains some Western European characters that have ASCII values that are larger than 127, you must build a new custom pipeline.

To build a new custom pipeline, follow these steps:  Open the Visual Studio 2005 IDE, and then add a new empty BizTalk Server project. Right-click the project, point to Add, and then click New Item. In the Categories list, click Pipeline Files, click Receive Pipeline, and then click OK. Drag the BTAHL7 2.X disassembler to the Disassemble area.

Note If the BTAHL7 2. X disassembler does not appear in the Toolbox window, follow these steps:  Right-click the toolbox surface, and then click Choose Items. In the window that appears, click the BizTalk Pipeline Components tab, click BTAHL7 2.X Disassembler in the Name list, and then click OK.</ol> </li> In the Pipeline Component Properties window, select either Western-European (1252) or UTF8 (65001) in the Encoding charset list.

Note You do not have to add ASCII encoding. ASCII is the default encoding that the HL7 receive pipeline provides. Other encoding options that appear in the Encoding charset list are not supported.</li> Save the encoding character set that you have just created, and then deploy the project.</li></ol>

To resolve this problem, you can use the new custom pipeline to replace the original BTAHL7 2.X receive pipeline. To do this, use BizTalk Server Administration.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Additional query words: BizTalk HL7 ISO 8859

Keywords: kbhotfixserver kbexpertiseadvanced kbqfe KB935347

-

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

© Microsoft Corporation. All rights reserved.