Article ID: 216049 - Last Review: October 26, 2006 - Revision: 4.1

XCLN: MAPIResolveName Does Not Properly Handle Multi-Byte Character Set (DBCS) Strings

This article was previously published under Q216049
Expand all | Collapse all

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.

RESOLUTION

To 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  (http://support.microsoft.com/kb/191014/EN-US/ ) XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack
Component: MAPI

Collapse this tableExpand this table
File nameVersion
Mapi32.dll5.5.2535.0

STATUS

Microsoft 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.

APPLIES TO
  • Microsoft Exchange Server 5.5 Standard Edition
Keywords: 
kbqfe kbhotfixserver kbbug kbfix KB216049
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
 

Article Translations