[a224932]

To all:

We are running BES 4.1 for GroupWise and as of yesterday morning, all emails have stopped coming to our BlackBerrys.

I did a search and found somethings on "At least one worker thread seems to be blocked", but found no solutions. Can anyone offer solutions that we can do to stop this error and have the emails continue to come to the BlackBerrys? I am a bit new to this and I am at a standstill.

Here is the error message we are getting:

reached the maximum of 10 restarts per 24 hours
[30000] (05/25 10:32:39):{0x204} Alarm::ThreadProc: Received an alarm message
[30000] (05/25 10:40:17):{0x590} EventLog::ThreadProc: Received notification, processing...
[30000] (05/25 10:42:34):{0x590} EventLog::ThreadProc: Received notification, processing...
[30000] (05/25 10:42:34):{0x590} Queuing alarm: BlackBerry Messaging Agent LR-BES Agent 1 (Application Event Log on LR-RECORD1): 05/25/2006 10:42:34 (AFFF4F02) -> At least one worker thread seems to be blocked (35)
[30000] (05/25 10:42:34):{0x204} Alarm::ThreadProc: Received an alarm message
[30000] (05/25 10:42:34):{0x590} Queuing alarm: BlackBerry Messaging Agent LR-BES Agent 1 (Application Event Log on LR-RECORD1): 05/25/2006 10:42:34 (6FFFC364) -> Some worker threads have been blocked for 35 health checks
[30000] (05/25 10:42:34):{0x204} Alarm::ThreadProc: Received an alarm message
[30000] (05/25 10:42:34):{0x590} Queuing alarm: BlackBerry Messaging Agent LR-BES Agent 1 (Application Event Log on LR-RECORD1): 05/25/2006 10:42:34 (6FFFC367) -> All worker threads of one of the pools seem to be blocked (35)
[30000] (05/25 10:42:34):{0x204} Alarm::ThreadProc: Received an alarm message
[30000] (05/25 10:42:39):{0x590} EventLog::ThreadProc: Received notification, processing...
[30000] (05/25 10:42:39):{0x590} Queuing alarm: BlackBerry Controller (Application Event Log on LR-RECORD1): 05/25/2006 10:42:34 (AFFF4FB6) -> EventID:afff4fb6'LR-BES' agent 1: will not restart - reached the maximum of 10 restarts per 24 hours

[Gareth.Hooper]

Check your calendaring aswell.
Try creating an appointment with invitee's and accept from Handheld.

You may find more issues there.
With so many users being supported, you maybe better off at this time to revert back to previous stable version of 4.0