XADM: Reversed Display Names May Not Be Resolved

Last reviewed: April 21, 1997
Article ID: Q147508

The information in this article applies to:

- Microsoft Exchange Server, version 4.0

SYMPTOM

When a first name such as 'Mary Anne' and a surname for a known recipient is typed on the TO: line in a Microsoft Exchange Client, the name is not resolved.

CAUSE

This problem occurs if the display name for the user is reversed as follows:

   User:         Mary Anne Smith
   Display Name: Smith, Mary Anne

When 'Mary Anne Smith' is typed on the TO: line, the display name is first referenced in order to resolve the address. In this case it will fail as the display name is 'Smith, Mary Anne'. The next phase will compare the typed name to the surname and given name of the recipient which is entered as first name 'Mary Anne' and last name 'Smith' in the order of last name first.

Due to the embedded space between 'Mary Anne', Exchange will simply see the name as 'Anne Smith' and the name resolution will fail.

This would not be the case if the name were 'Mary Smith' as Exchange would be able to see both the first and last names properly.

WORKAROUND

If your system is configured to use reversed display names, the recommended option would be to enter the first name as simply 'Mary' and use 'Anne Smith' as the last name on the user's mailbox properties in the Microsoft Exchange Administer program. This will result in the name being properly resolved when 'Mary Anne Smith' is typed on the TO: line in a Microsoft Exchange Client.

Additional query words:
Keywords : kbusage XADM
Version : 4.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.