In ZCB 6.0.8 installation procedure(see below) has been simplified so that installation of MAPI/CDO is no longer necessary:-install Outlook 2007 -install standalone CDO(Download details: Collaboration Data Objects, version 1.2.1) -install ZCB 6.0.8 (grab latest one from website) -create MAPI profile...

The connector that you are using is very old. I would suggest to upgrade to the latest ZCB-6 which works against ZCS 6.0.2 or higher. Or atleast upgrade to ZCB 5.0.24 wich works against ZCS 5.x.Also you maybe interested in ZCB 6.5 which has support for BES 5.xLatest connector downloads can be found ...

What version of connector are you using? Is HKLMSoftwareimbra urnOffInboxFailures (DWORD) set to 1 on BES machine?To enable zcb logging please follow this article: ZCB and BES Logs - BlackBerry - Zimbra :: WikiIn case if you don't see anything obvious, please don't hesitate to contact suppo...

>I'm slightly disatisfied with this solution. Even the old linked version of >MAPI/CDO does not install after Outlook 2007 (ok, thats not the proposed >order of installation).Right. Installation order is important and MAPI/CDO has to be installed before Outlook. This way you won't get errors...

Windows Server 2003 64 bit is not yet supported. I would suggest to try the same procedure on 32 bit version of Windows Server 2003.

Server 2003 R2 32 bit is supported. We may need to clarify the document.

Just opened the bug, we will need to test and certify zcb with 64 bit of server 2003.
Bug 49284 – test and certify zcb with Windows Server 2003 64 bit

Please follow recommendations specified by RIM in the latest compatibility matrix (link below). ZCB shares the same set of recommendations, except the fact that it's never been tested with 64 bit version of Windows Server 2003.http://na.blackberry.com/eng/support/software/server_exchange_ver_jul...

Actually, this version does eliminate runtime dependency on Outlook. Although installation of Outlook is still required, in zcb 6 BB agent doesn't launch Outlook as a process anymore.

Although i can't reproduce it myself, i opened the bug https://bugzilla.zimbra.com/show_bug.cgi?id=48727 and submitted the fix which is the main suspect behind the error message in question. Please contact support@zimbra.com or myself(eugene@zimbra.com) to obtain zcb build containing this fix.