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 queue information, error <error code>.
|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?
|Our approach: This information is only available to subscribers. An example of Our approach|
- Error code: 0x800706a6 - See ME810861.
- Error code: 0x80041001 - See ME810861.
- Error code: 0xc00402be - See ME810861, ME834318, and ME889180.
- Error code: 0x80004005 (Error code 0x80004005) - See ME889180.
As per Microsoft: "The Microsoft Exchange System Attendant was unable to query Window Management Instrumentation (WMI) for instances of ExchangeLink class. This class is provided by the Exchange provider (exwmi.dll). This event does not necessarily indicate an error condition. It can occur on an otherwise properly functioning server". See MSEX2K3DB for additional information on this event.
Error: 0x80041001 = "WBEM_E_FAILED" - Generic Failure. As per ME295563, this error is cause if the performance object has multiple indexes registered under the multiple string "Counter" value, then the WMI Performance Provider may be using the wrong index. The article provides the fix.
|Private comment: Subscribers only. See example of private comment|
|Links: ME295563, ME810861, ME834318, ME889180, Error code 0x80004005, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated