XCLN: Searching for Manager Produces MAPI Error

 Last reviewed: August 28, 1997
Article ID: Q166590

The information in this article applies to:

  • Microsoft Exchange Active Server Messaging component

SYMPTOMS

If no manager is set for a particular recipient, when a messaging developer tries to obtain a recipient's manager, the following error occurs: 

   MAPI_E_NOT_FOUND
An empty value should be returned.

The problem occurs when a messaging developer runs the Microsoft Visual Basic 5.0 Active Messaging Autotest Script on Microsoft Exchange Server 5.0 build 1558 (as declared in Help About).

RESOLUTION

With the release of Service Pack 1, Microsoft will check for MAPI_E_NOT_FOUND and shadow it to return success. Because the return value for the object is initialized to NULL at the outset, the result returned will be empty.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange Server 5.0 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

Keywords          : kbbug5.00 kbfix5.00.sp1 XCLN
Version           : 5.0
Platform          : WINDOWS
Issue type        : kbbug

================================================================================

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: August 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.