XCLN: Active Messaging App Running as Service Fails

 Last reviewed: December 18, 1997
Article ID: Q166550

The information in this article applies to:

  • Microsoft Exchange Windows 3.x client version 5.0
  • Microsoft Exchange Windows 95 client version 5.0
  • Microsoft Exchange Windows NT client version 5.0

SYMPTOMS

When you attempt to run an Active Messaging Application from a Windows NT Service (for example, AT Scheduler) the following error message may appear. 

   MAPI_E_NOT_FOUND
The error message is returned from the Active Messaging Session Object when a profile name is passed. The application runs successfully when it is not being run in a Windows NT service.

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

MORE INFORMATION

Running Active Messaging as a Windows NT service requires additional configuration to initialize a MAPI session. For more information, please refer to the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q177851
   TITLE: HOWTO: Build a VB/Messaging Application to Run from a Service

Additional query words:
Keywords : kbbug5.00 kbfix5.00.sp1 XCLN kbusage
Version : 5.0
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

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