XADM: Event Service Won't Start If Alternate PF Server Selected

 Last reviewed: March 5, 1998
Article ID: Q182082
The information in this article applies to:
  • Microsoft Exchange Server, version 5.5

SYMPTOMS

When you configure a different server to be the Public Folder Server, the Event Service fails to start and logs the following sequence of events in the Windows NT Event Log: 

   Event ID   : 0
   Source     : MSExchangeES
   Type       : Informational
   Category   : General
   Description: The Microsoft Exchange Event Service (5.5.1960.3)
                Started successfully.

   Event ID   : 5
   Source     : MSExchangeES
   Type       : Error
   Category   : General
   Description: An unexpected MAPI error occurred. Error returned
                was [0x80004005].

   Event ID   : 1
   Source     : MSExchangeES
   Type       : Informational
   Category   : General
   Description: The Microsoft Exchange Event Service stopped successfully.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. We are researching this problem and will post additional information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

It makes no difference what version the selected Public Folder Server is (4.0, 5.0, or 5.5). The results are the same. 

Keywords          : XADM kbbug5.50
Version           : WINDOWS:5.5
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: March 5, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.