LDAP Version 2 Clients Receive Extended Characters Instead of IA5 for Search Queries (196772)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q196772 SYMPTOMS
If Netscape Communicator version 4.5 is performing a Lightweight Directory
Access Protocol (LDAP) search request against an Exchange Server computer
for a directory entry containing extended characters, these characters are
not displayed correctly.
CAUSE
Netscape Communicator 4.5 is a LDAP version 2 client and so expects to
receive IA5 characters only.
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
The English version of this fix should have the following file attributes or later:
Component: Directory
This hotfix has been posted to the following Internet location as Psp2diri.exe (x86) and Psp2dira.exe (Alpha): STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange Serverversion 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.MORE INFORMATION
Outlook Express 4.0 has no such problem because it is an LDAP version 3
client and so supports receiving UTF-8 characters.
| Modification Type: | Major | Last Reviewed: | 9/24/2003 |
|---|
| Keywords: | EXC55SP3Fix kbbug kbfix kbQFE KB196772 |
|---|
|