This article was previously published under Q303310
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
The Microsoft BizTalk Server 2000 EDIFACT parser cannot convert DBCS characters correctly. If the BizTalk Server EDIFACT parser parses an EDIFACT document that contains DBCS characters, these characters translate as "garbage" characters.
The Microsoft BizTalk Server 2000 EDIFACT parser does not support the use of code pages that can properly convert documents that contain DBCS characters.
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack
Microsoft has confirmed that this is a problem in BizTalk Server 2000. This problem was first corrected in Microsoft BizTalk Server 2000 Service Pack 1a.
Microsoft BizTalk Server 2000 SP1a updates the EDIFACT parser and serializer to accept a registry key, so that if the EDIFACT document header is UNOA, it will define a code page, other than the default code page, to be used to convert the data. When the @EDIFACTUNOACodepage registry value is added to the set of values that BizTalk Server defines, it has a default value of 0, and when it is set to zero, it uses default behavior. If you set it to some other value, that value is assumed to be the code page to convert the resultant data. The code page change is global. All EDIFACT data passing through that BizTalk Server 2000 computer processes data according to the @EDIFACTUNOACodepage code page. You must manually create this registry entry to allow the EDIFACT parser to use a non-default code page. To do this, perform the following steps:
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Start Registry Editor (Regedt32.exe).
Locate and click the following key in the registry: