Microsoft KB Archive/816068

= XML declarations that BizTalk Server generates do not match the file encoding =

Article ID: 816068

Article Last Modified on 5/21/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition

-





SYMPTOMS
If you set Microsoft BizTalk Mapper to generate an XML declaration in the outbound document, the document may be encoded as UTF-8, although the XML declaration indicates that the document is encoded as UTF-16.



CAUSE
When BizTalk Mapper generates the outbound document, the data is encoded as UTF-16. However, the encoding of the document may change, depending on the transport that is used in the messaging port. The XML declaration is not updated after the mapping stage. Therefore, the declaration still indicates that the document is encoded as UTF-16.



RESOLUTION
If your output document must be encoded in a specific format, you must process the data outside Microsoft BizTalk Server to use a specific encoding scheme.

The BizTalk Server online documentation includes a Microsoft Visual Basic Scripting Edition (VBScript) sample that illustrates how to change the encoding of a document. For more information, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/ms935016.aspx



STATUS
This behavior is by design.



Steps to reproduce the behavior

 * 1) Use BizTalk Mapper to create a new map between two document specifications. On the Tools menu, click Options. On the XSLT Output tab, set the Omit XML declaration option to no.
 * 2) Create a new messaging port and a new channel by using the map that you created in step 1. Select file transport for the port.
 * 3) Submit a document to the channel. When an output file is generated, notice that it is encoded as UTF-8.

Keywords: kbprb KB816068

-

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

© Microsoft Corporation. All rights reserved.