Article ID: 885897 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When an HTTP request message is encoded with a Unicode character set (UTF8 or UTF16), the Microsoft BizTalk Server 2004 HTTP adapter will pre-append the byte order mark (BOM) to the message before it sends the message out to the partner. The partner may not be able to recognize and process the BOM.
Service pack informationTo resolve this problem, obtain the latest service pack for BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/888751/ )How to obtain the latest BizTalk Server 2004 service pack
Hotfix informationA supported hotfix is 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 software update that contains this hotfix.
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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesNo prerequisites are required.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 tool in Control Panel.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Date Time Version Size File name -------------------------------------------------------------------------------------- 19-Apr-2004 21:26 3.0.5283.0 144,896 Btshttpreceive.dll 19-Apr-2004 21:26 3.0.5283.0 1,021,440 Btsmsgcore.dll 19-Apr-2004 20:50 3.0.5283.0 32,768 Microsoft.biztalk.cachingservice.dll 19-Apr-2004 20:50 3.0.5283.0 720,896 Microsoft.biztalk.globalpropertyschemas.dll 19-Apr-2004 21:26 3.0.5283.0 65,536 Microsoft.biztalk.httptransport.dll 19-Apr-2004 20:57 3.0.5283.0 49,152 Microsoft.biztalk.messaging.dll 19-Apr-2004 20:50 3.0.5283.0 217,088 Microsoft.biztalk.pipeline.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in BizTalk Server 2004 Service Pack 1.
This fix only affects HTTP request messages. HTTP response messages may still contain BOM even after the hotfix is applied. If you do not want BOM in HTTP response messages, you can use a custom pipeline component to remove it.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 885897 - Last Review: January 17, 2015 - Revision: 3.2