OL2000: DCR: The LDAP Provider Places the Common Name Attribute in the 'PR_DISPLAY_NAME' Property (277901)
The information in this article applies to:
This article was previously published under Q277901 SYMPTOMS When you use the Lightweight Directory Access Protocol
(LDAP) provider that comes with Outlook 2000 with Active Directory, the common
name (CN) attribute may be placed in the PR_DISPLAY_NAME property of a MAPI message. If you are accustomed to the
Microsoft Exchange 5.5 directory, you may expect that the Display-Name
attribute is used here. Naming conventions that assign ID numbers to the common
name (CN) attribute of an object may yield messages that appear to be from a
number rather than from a person.
The following pseudo-code represents the logic that is used
to resolve the name of an object in the LDAP directory that is being searched:
Use (if available)
DisplayName (display-name)
else
CommonName (cn | commonName)
else
SurName + GivenName (givenName + sn | surname)
else
SurName (sn | surname)
else
CompanyName (co | organizationName | o)
else
EmailAddress (configurable)
else
Least significant component of DN
CAUSE The Exchange 5.5 directory and the Active Directory use
different LDAP names for the displayName attribute. Exchange 5.5 calls the attribute "Display-Name"
(without quotation marks), while Active Directory calls the attribute
"displayName" (without quotation marks). For a resolved name in a new message,
this LDAP provider was designed to return the Display-Name attribute for an
object (if it exists) in the PR_DISPLAY_NAME property of the message. This is what happens with the Exchange
5.5 directory, where the LDAP name for this attribute is
Display-Name.
By contrast, in the Active Directory (which is used by
Microsoft Exchange 2000), the attribute in the schema is named displayName, not
Display-Name, and the LDAP provider returns the common name (CN) when it does
not find Display-Name. Because the common name (CN) is returned, the PR_DISPLAY_NAME property on the message may be given an unexpected or undesirable
value.
The MAPI - Microsoft LDAP directory provider uses the
Display-Name attribute (which exists in an Exchange 5.5 directory) instead of
the displayName attribute (which exists in the Active Directory). If the
Display-Name attribute does not exist, then the provider is coded to use the
common name (CN) attribute. This was a design decision by the authors of the
LDAP MAPI provider to accommodate the Exchange 5.5 directory. When the
directory points to the Active Directory, the display name property is stored
in an attribute named displayName, not Display-Name, and the common name (CN)
is returned.
RESOLUTION The LDAP provider for MAPI places the Display-Name or the
displayName attribute in the PR_DISPLAY_NAME property before it stops and searches for the common name (CN) or
other attributes. To resolve this problem, obtain the latest
service pack for Microsoft Office 2000. For additional information, click the
following article number to view the article in the Microsoft Knowledge Base: 276367 OFF2000: How to Obtain the Latest Office 2000 Service Pack Before you apply this fix, update Microsoft Office
2000 to Service Release 1/1a (SR-1/SR-1a). To obtain Microsoft Office 2000
SR-1/SR-1a, click the article number below to view the article in the Microsoft
Knowledge Base:
245025 OFF2000: How to Obtain and Install Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a)
The English-language version of this fix should
have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------
01/08/2001 02:37p 1.00.03.0028 98,304 Bjsrch32.dll
STATUSMicrosoft
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
Microsoft Office 2000 Service Pack 3 (SP-3).
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbBug kbfix kbOffice2000SP3Fix KB277901 |
|---|
|