Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

BUG: The TargetCharset value in an XMLTransmit pipeline configuration may not take effect as expected in BizTalk Server 2006


View products that this article applies to.

Symptoms

In Microsoft BizTalk Server 2006, the TargetCharset value for an XML Transmit pipeline may not take effect as expected.

For example, you receive a message that uses the UTF-8 encoding format. However, you want the outgoing message to use the UTF-16 encoding format. Therefore, you set the TargetCharset value in the XMLTransmit pipeline to Big-Endian-UTF16 (1201). However, the outgoing message may unexpectedly use the UTF-8 encoding format.

↑ Back to the top


Workaround

To work around this issue, use one of the following methods.

Method 1: Use a custom pipeline

To work around this issue, use a custom pipeline to send the messages. For example, set the Target charset property in the XML assembler component of the custom pipeline as follows:
  • To use the UTF-8 encoding format, set the Target charset property to UTF-8 (65001).
  • To use UTF-16 encoding format, set the Target charset property to Big-Endian-UTF16 (1201) or Little-Endian-UTF16 (1200).

Method 2: Use an orchestration

To work around this issue, use a construct shape in an orchestration to correctly set the encoding value. For example, add a MessageAssignment shape to a new orchestration. Next, double-click the MessageAssignment shape. Then, type the following code in the BizTalk Expression Editor.
<Message_Name>(XMLNORM.TargetCharset) = "unicode";

↑ Back to the top


Status

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

↑ Back to the top


Keywords: KB939550, kbbug, kbcode, kbbts, kbbtsorchestration, kbtshoot

↑ Back to the top

Article Info
Article ID : 939550
Revision : 3
Created on : 10/31/2007
Published on : 10/31/2007
Exists online : False
Views : 605