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.
At least one worker thread seems to be blocked (<value>).
|English: Request a translation of the event description in plain English.|
I received this event on Windows 2003 SP1 and Blackberry 3.6 communicating with Exchange 2003 SP2. With W2K3 SP1 there's a well-known issue with the tcpip.sys file; applying the hotfix from ME898060 fixes this issue. Since it relates directly to communications dropping to and from the Exchange server, and BES does not know what to do with MAPI connections that fail (they should be reset but they are not) these MAPI threads become deadlocked. Redirection comes to a halt. Rebooting the BES server will fix this but only temporarily. Since applying the hotfix, the issue has not come back en masse although moving mailboxes does seem to cause this event temporarily as well. If you are migrating to other Exchange servers turning off the old servers without rebooting BES will cause this as well.
See "Worker Thread Issues, MAPI, and BlackBerry Enterprise Server v3.6" for a paper on this issue from BlackBerry.
|Private comment: Subscribers only. See example of private comment|
|Links: ME898060, Worker Thread Issues, MAPI, and BlackBerry Enterprise Server v3.6|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated