[MisterGriffiths]

Since moving all our BlackBerry users (on BES 5.0.3 MR4) over to Exchange 2010 (SP1 RU3) the MAGT logs appear to have an increased number of log entries relating to *** Busy Working *** Worker Thread activity showing the event:

CHECK_FB_CACHE_EXPIRY

We are also seeing the same event occasionally causing *** No Response *** Worker Thread activity which (after the customary 6 health checks), causes the Agent to stop and re-spawn.

At first we thought that users were hitting the' View Availability' button within a received appointment which contains lots of other users but we aren't sure now if it isn't just something that is happening of its own volition.

Anyone else seeing lots of Free Busy activity in their logs?

[knottyrope]

CDO or EWS?

What version CDO are you using?

[MisterGriffiths]

Originally Posted by knottyrope

CDO or EWS?

What version CDO are you using?

Well, it's SP3 and native Exchange 2010 so it should be using EWS. We do have CDO 1.2.1 (6.5.8211.0) running on the BES Application Servers.

We've checked all the usual stuff (permissions, IIS, certificates, etc).

I was more just interested to know if anyone else ever sees these entries in their own MAGT logs.

[knottyrope]

i think you need to upgrade CDO to 8244 if on SP1 RU3

[MisterGriffiths]

When we deployed, I'm pretty sure the compatibility matrix had 8211 as the recommended version. Actually I don't think 8244 had been released.

Have just check the matrix again and you are correct, recommended is now 8244, although 8211 is the only other version listed as supported.

I have an upgrade window in June to upgrade to MR7, might be worth doing CDO at the same time.

We actually have this open with RIM at the moment so I'm surprised they haven't mentioned this themselves.

[knottyrope]

check out this link too
KB20028-How and when to enable Microsoft Exchange Web Services for calendaring components on BlackBerry Enterprise Server

[MisterGriffiths]

KB31144-Non responsive worker threads on the BlackBerry Mailbox Agent due to high CPU usage

New KB posted 4 days ago.