FIX: XLANG Event Monitor Displays Garbage Characters When Port or Action Name Contains Double-Byte Characters (297593)



The information in this article applies to:

  • Microsoft BizTalk Server 2000

This article was previously published under Q297593

SYMPTOMS

When you use the XLANG Event monitor to monitor an XLANG schedule that has a port or action name with double-byte characters, the XLANG event history may return garbage characters in some of the event fields such as SourceEnter, SourceLeave, and PortID.

RESOLUTION

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 the Microsoft Knowledge Base:

299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in BizTalk Server 2000 Service Pack 1.

MORE INFORMATION

The XLANG Event Monitor is accessible from Program Files\Microsoft BizTalk Server\SDK\XLANG Tools\XLANGMon.exe.

This issue has been observed in the Japanese version of BizTalk Server 2000 when it is running on the Japanese version Windows 2000.

Modification Type:MajorLast Reviewed:10/22/2003
Keywords:kbBizTalk2000SP1fix kbbug kbfix KB297593