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.
The MAD Monitoring thread was unable to read the state of the services, error '<error number>'
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange System Attendant (MSExchangeSA) service?
As per Microsoft: "The Monitoring thread will recover from these errors if they are isolated. If you receive more than six of these events every hour, then the underlying cause needs to be investigated". See MSEX2K3DB for additional information about this event.
This issue may occur if the workflow event sink, Cdowfevt.dll, is not correctly registered. See ME326011 and ME810861 for more details.
|Private comment: Subscribers only. See example of private comment|
|Links: ME326011, ME810861, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated