[SOLVED] Help! After installing 5.0.19, BES stopped talking to handhelds.

Last night 01.com updated our Zimbra NE installation from 5.0.10 to 5.0.19_GA_3083.MACOSXx86.NETWORK Sep 18, 2009.

I took the time this afternoon to update our new 'BES' (running BlackBerry Professional Software 4.1.4B) from the BETA3 ZCB to the 5.0.19 ZCB.

About 2:21pm CST, I followed all the upgrade instructions on p25 of "September 2009 Zimbra Mobile Connector for BES - Small Business Edition 5.0.19". HOWEVER since that time NONE of the 6 devices on that BPS have communicated with the server: the Last Contact Time being around 2:21, almost 4 hours ago.

I have tried stopping and restarting the BlackBerry Controller, and restarting the server completely, but there is no change. Hard to see anything useful in the logs, I'm not really a Windows admin. Any help or insight would be very welcome!!!

Chris

Please post MAGT log file.

Attachment 3455

I pulled this from today and yesterday

Based on the logs, BES experienced problem to resolve BB users in the GAL. First thing to try to resolve this would be the following:

BES set to use the local contacts list instead of the GAL - Zimbra :: Wiki

Alternatevly, there is a button called 'Force GAL sync' that can be found on zcb logging control (type zcologctl.exe in command prompt). Pressing on this button will initiate GAL sync immediately. Please note that it is important for BB controller and BB manager to be running before pressing the button as GAL sync depends on those two processes.

If nothing helps, please open up 'BlackBerryServer', 'BlackBerryManager' profiles with Outlook and manually add problematic contacts to the GAL.

It opened the floodgates to an extent, but kind of seems to be stopped on what looks like threads being 'blocked'.

It starts crapping out at this line:
[30247] (12/03 15:10:33.781):{0x10F0} Server stats - Msgs: Forwarded 21294, Sent 1988, Pending 289, Expired 0, Filtered 47

Log attached:
Attachment 3456

Thanks for all your help so far.

Messages are slowly rolling out to users still. If the 'worker thread' issues lighten up after the server has a chance to catch up overnight, I will follow-up with the status here.

Thanks eugener,
Chris