XADM: Cannot Open Custom Recipient in Administrator

Last reviewed: April 21, 1997
Article ID: Q143377
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

When you try to open a Custom Recipient that has been loaded into Microsoft Exchange by directory synchronization (dirsync) from either Microsoft Mail 3.x or Microsoft Mail for Appletalk Networks and it has non teletex characters ($, ~, ^, $, or #) in the Common Name portion of the Distinguished Name, the following error might be displayed:

   The object cannot be found in the directory. This may be
   because replication has not completed.
   Microsoft Exchange Directory
   ID No. c1010aae

CAUSE

Some dirsynced addresses contain non teletex characters in a field that the Microsoft Exchange Directory Synchronization Agent (DXA) uses for the alias field. This field is also used for the Common Name portion of the Distinguished Name in the Microsoft Exchange Directory. The Microsoft Exchange Administrator program uses character mapping (ANSI) to handle the characters, but the DXA converts these characters differently. The end result is that the Microsoft Exchange Administrator program cannot open these entries.

RESOLUTION

The DXA has been changed to use the same method of character conversion as the Microsoft Exchange Administrator program.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Server U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


Additional query words: HotFix
Keywords : kbbug4.00 kbfix4.00.sp2 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.