XCLN: Active Messaging App Running as Service Fails

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q166550

Expand all | Collapse all

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.

Back to the top

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

Back to the top

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:

177851 (http://support.microsoft.com/kb/177851/EN-US/ ) HOWTO: Build a VB/Messaging Application to Run from a Service

Back to the top

APPLIES TO

Microsoft Exchange Client 5.0

Back to the top

kbbug kbfix kbusage KB166550

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top