XCLN: MAPIResolveName Does Not Properly Handle Multi-Byte Character Set (DBCS) Strings (216049)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q216049 SYMPTOMS
A simple Messaging Application Program Interface (MAPI) application passes a Double-Byte Character Set (DBCS) string to the MAPI call MAPIResolveName(). MAPIResolveName fails when a two-byte DBCS character contains 0x5b or 0x5c as one of its bytes.
CAUSE
A supporting routine used by MAPIResolveName() was not written to properly handle DBCS strings, and mistakenly interprets the bytes 0x5b and 0x5c as '[' and '\' respectively.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack
Component: MAPI STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.
| Modification Type: | Major | Last Reviewed: | 4/7/2006 |
|---|
| Keywords: | kbQFE KBHotfixServer EXC55SP3Fix kbbug kbfix KB216049 |
|---|
|