Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Error <error> connecting to the <service> Service.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Information Store service?
On our Exchange 2007 server, the MS Exchange Store didn't start with error message ''Error 0x8004010f connecting to the Microsoft Active Directory. '' Article TB885057 solved our problem. Nobody understood why this setting was changed.
- Error: 0x96e, Service: Microsoft Active Directory - This problem occurs because the domain controller and other Exchange-Server-dependent services do not start completely when Exchange 2007 tries to start. See ME940845 for details.
- Error: 0x8004010f, Service: Microsoft Active Directory - This behavior may occur if the organization name that you select during setup contains the forward slash mark (/) character. See ME329599 for more information on this problem.
- Error: 4015, Service: Microsoft Exchange Information Server Directory - The Directory service will not start if the system date is later than January 17, 2038. See ME154595 for details about this problem.
- Error: 0x80004005, Service: Microsoft Exchange Server Directory - This behavior may occur because the information store database is not initializing properly. See ME322315 to solve this problem.
- Error: 0x80004005, Service: Microsoft Active Directory - You may not be able to mount Exchange 2000 information store databases and this event is logged. See ME314294 and ME822579 for details.
- Error: 0xfb5, Service: Microsoft Exchange Server Directory - This issue can occur if the Information Store service has been configured to log on as a system account or to use the Local System account. See ME288952 to solve this problem.
- Error: 0xfaf, Service: Microsoft Active Directory - This behavior can occur because you do not have a global catalog in the forest or the connection to the global catalog is lost. See ME303186 and ME823163 to find out how to fix this problem.
- Error: 0xfaf, Service: Microsoft Exchange Server Directory - This issue can occur if the server is renamed after Exchange Server installation; some values in the MSExchangeIS key contain the name of the test server. See ME248124 to solve this problem.
See ME187869 for additional information about this event.
- Error: 0x80004005, Service: Microsoft Active Directory - This problem may occur if the global catalog server is located in a different domain than the Exchange 2000 computer. See ME320039 and ME328662 for more details.
- Error: 0x80004005, Service: Microsoft Active Directory - This issue may occur if the "Manage auditing and security log" permission (SeSecurityPrivilege) is removed from the Exchange Enterprise Servers group on some domain controllers or on all domain controllers. See ME896703 for details on this issue.
See MSEX2KDB for additional information on this event.
You Cannot Install a Second Exchange 2000 Server in an Exchange 2000 Server Site and Event ID 9525, 1121, and 5000 Error Messages Are Logged.
ME305392 says "This issue may occur if authenticated users do not have read access in the Domain container or in the Configuration container in Active Directory" and provides a fix.
|Private comment: Subscribers only. See example of private comment|
|Links: ME154595, ME187869, ME248124, ME288952, ME303186, ME305392, ME314294, ME320039, ME322315, ME328662, ME329599, ME822579, ME823163, ME896703, ME940845, MSEX2KDB, TB885057|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated