XADM: Event Service Will Not Start If an Alternate Public Folder Server Is Selected
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.
The Event Service only needs to be running on a server with a local Public
Store. If the server logging the above errors has another server listed on
the Private Information Store property page as the "Public folder server",
then the Event Service should be dissabled or uninstalled to prevent the
above events.
Keywords : XADM kbbug5.50
Version : WINDOWS:5.5
Platform : WINDOWS
Issue type : kbbug