Blackberry2Droid Version 1.0.2 Released

After a few months with no development I’m pleased to announce that BlackBerry2Droid has reached version 1.0.2. With the latest version comes support for messages encoded with UCS-2 (a way of converting readable characters to numbers that pre-dates UTF-16). This results in support for languages that use non-Latin alphabets such as Cyrillic, Greek etc.

A bug where the sender/receiver of messages has also been corrected.

Support for different languages has been a long standing feature request. If it’s something you’ve found useful, please encourage others to check it out by tweeting about it or sharing it on Facebook/G+.

Head on over to the Blackberry2Droid page to download the latest version.
Continue reading Blackberry2Droid Version 1.0.2 Released

BlackBerry 2 Droid Updated with BBB support

RIM have two file formats for BlackBerry backups, IPD and BBB. As of today BlackBerry2Droid now supports the BBB file format, head over to the updated BlackBerry2Droid page and download version 1.0.1 to take advantage of the new functionality.

BlackBerry 2 Droid will allow you to transfer messages from a BlackBerry Backup file and import them into your Android phone.
Continue reading BlackBerry 2 Droid Updated with BBB support

Blackberry calendar not synchronising from device to Exchange

An issue was recently escalated to me where BES users were experiencing problems with their Blackberry calendar synchronisation. Appointments would appear on the device if they were created in Outlook, but not the other way around.

Blackberry Enterprise Server (BES) was running 5.0.3 on a Windows 2003 Virtual-Machine (VMware ESX).

Looking back over the logs on the server, the problem could be traced back to the installation of BES 5.0 Service Pack 3. The Changes in 5.0 SP3 didn’t show anything that could obviously cause this, so the first task was to update MAPI CDO to the latest version.

Digging throught the Messaging Agent log files yielded the following:

[40000] (01/06 00:00:04.871):{0x268} Failed to start CDO helper 070FD658 in StartCalHelper, retcode = 128
[40000] (01/06 00:00:04.871):{0x268} {} StartCalHelper() failed in RunCalHelper
[40000] (01/06 00:00:04.871):{0x268} {} CDO helper 078FD658 returned error '100' failed for LongTermEntryId=0 in LaunchCalHelper
[40000] (01/06 00:00:04.950):{0x268} {} Unable to launch CDO helper in SynchronizeHelper
[40000] (01/06 00:00:04.950):{0x268} {} Unable to process message with LongTermEntryId=0 in SynchronizeHelper
[20216] (01/06 00:00:04.950):{0x268} {} Synchronize() failed: ERR_FAIL, Tag=2242466
[40000] (01/06 00:00:04.950):{0x268} {}-UserControl::SlowSyncComplete-Entering SessID=4fce8f76
[40000] (01/06 00:00:04.950):{0x268} {}-UserControl::SlowSyncComplete-Exits result=OK
[40000] (01/06 00:00:04.950):{0x268} {}-HandleAppointmentToSynchronize-Exit-rc=Error
[40279] (01/06 00:00:04.950):{0x268} {} SubmitToRelaySendQ, Tag=2242466

After trying everything I could possibly think of, the problem turned out to be outdated NIC drivers. BES was running under VMware ESX using an emulated e1000 NIC which shows up in Windows as an “Intel PRO/1000 MT”. The out-the-box driver was version (from 2002). The latest version (from 2008) can be downloaded from the Intel website.

Updating to the latest driver resolved the problem (amazingly).