XADM: Event Service Will Not Start If an Alternate Public Folder Server Is Selected

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q182082

Expand all | Collapse all

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.

This behavior is by design.

When you change Server A's private store to use the public store on Server B, this change is not complete until the DS changes have replicated from Server A to Server B, which takes 10 to 15 minutes (or whatever the replication latency of your site is). After that time, the Event Service should start normally.

As an alternative, you should be able to force a DS replication update in the site to make this happen sooner.

APPLIES TO

Microsoft Exchange Server 5.5 Standard Edition

Back to the top

kbbug KB182082

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