[sniffs]

I'm seeing this at least once a week, it's kind of frustrating that after YEARS of being a BES admin, that RIM can't seem to figure out how to make a BES work without having to have it rebooted at least a couple times a week. I've been trying to google these errors and coming up with little useful information.

"Thread: main timer thread appears to be blocked"

"Failed to get thread context for suspended thread Handle=0x754"

"Failed to output thread call stack (thread Id=0x1868, Handle=0x754)"

All 5 BES agents then die and fail to restart unless I reboot.

Win2k8r2 64bit, mixed exchange 2007 and 2010 boxes. BES 5.0.2 mr1 (Bundle 51) built to exact prerequisites that RIM suggests.

I've not tried to rebuild the mapi profile yet.

According to RIM, their fix for the timer being blocked is to install 5.2 Mr2, but I already have it installed. Any other ideas?

[RadHaz75]

install sp3 mr1.

also, do you have the latest mapi/cdo (6.5.8211.0)?

Download details: Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

KB15779-How to install or upgrade the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

[chubby_nubby]

Have you set up a new throttling policy for exchange 2010 for the besadmin account?

[sniffs]

How can I verify that CDO is installed correctly? I only see it in c:\program files(x86)\exchangecdo

I think this might be a CDO/MAPI issue so thats why I'm going to be recreating the MAPI, but if you just install the CDO pack, it'll install but how can I verify it's registered?