Originally Posted by glamprecht
I started out with a one way sync issue. Entries into any bb would not make it to Outlook. Entries from Outlook would make it successfully to bb.
During the course of troubleshooting it seems to have gotten worse. Now calendars do not talk at all. Everything else seems to work just fine. Searching forums and internet brought up many, many posts about this issue. Most pointed to mapi and cdo files matching.
We are running exchange 2003 with Sp2. BES Enterprise 4.1 with Exchange SP2 installed.
The BES server was showing a MAPI.DLL of 6.5.7638.1 and CDO.DLL of 6.5.7651.61.
The Exchange server was showing the same version MAPI.DLL but a CDO.DLL of 6.5.7654.12.
I tried to make them the same by unregistering them, placing the highest like one in the exchsrvr\bin dir in both servers and re-registering. Now I seem to have lost all calendar functions. Any ideas?
The Collaboration Data Object (CDO) is an object library created by Microsoft that developers can use to allow communication with Microsoft Exchange Server Global Address Lists (GALs), mailboxes, and public folders. The cdo.dll file creates these capabilities and is used in conjunction with the Messaging Application Programming Interface (MAPI). In order to use the cdo.dll file for various tasks related to calendars (for example, creating, modifying, and deleting meeting requests), it must be present on the BlackBerry® Enterprise Server for Microsoft® Exchange.
Although it is common practice for cdo.dll file versions to match on the BlackBerry Enterprise Server and the Microsoft Exchange Server, it is not necessary. The BlackBerry Enterprise Server only uses the cdo.dll file that is installed on the BlackBerry Enterprise Server to process calendar items. Whenever there are calendar or scheduling issues for BlackBerry smartphone users, the cdo.dll file should only be updated on the BlackBerry Enterprise Server. It is not necessary to update the cdo.dll file on the Microsoft Exchange Server.
The cdo.dll file version on the BlackBerry Enterprise Server is determined by the version of Exchange System Manager installed on the BlackBerry Enterprise Server. Each version of Exchange System Manager will have a specific MAPI32.dll file. Usually, the same version of the MAPI32.dll and cdo.dll files are installed on the BlackBerry Enterprise Server. However, if a cdo.dll file hotfix has been applied to the BlackBerry Enterprise Server, the cdo.dll file version on the BlackBerry Enterprise Server may be later than the MAPI32.dll file version installed on both the Microsoft Exchange Server and the BlackBerry Enterprise Server.
In a mixed mode environment, where different versions of the Microsoft Exchange Server run simultaneously (for example, Microsoft Exchange 2000 and 2003), the MAPI32.dll file version on the BlackBerry Enterprise Server should be equal to or later than the latest MAPI32.dll file version of the Microsoft Exchange Servers where BlackBerry smartphone users are located. For example, if there are BlackBerry smartphone users on an Microsoft Exchange 2003 Server, the cdo.dll file version on the BlackBerry Enterprise Server should be based on the MAPI32 subsystem of the BlackBerry Enterprise Server (the MAPI32 subsystem is based on the version of MAPI32.dll file found on the Microsoft Exchange 2003 Server). The cdo.dll file may be a later version on the BlackBerry Enterprise Server depending on whether a hotfix has been applied.
you need you update your CDO version and it should be same or higher from your exchange cdo version.
you can download latest cdo version from MS website