Hi,

This is my first post here, so please go easy on me.

Some background first:

I look after approximately 50 Blackberry’s connected to a BES which is linked to Domino.

I have successfully added the Nokia to the BES and have tested the email side of things with no problems. After running "connect" thru the Blackberry Connect software, the calendar will start uploading to the device. At approximately 260 entries I receive a "Device Communication Error"....Communication with the device has failed.

So far I have done the following:

Checked the OS: Ver 5.22 (*#0000#)
Formatted the handset
Reloaded the BB connect client: S80_BlackBerry(5.249.0).SIS

Could it be that some calendar entries in Lotus Notes be corrupt??

I'm really lost on this and any help would be greatly appreciated.


Thanks,

Phill

Are your users calendar entries crowded?

In the sync software, goto the Settings option, then select the Calendar/To Do tab, then change the Range. I think by default it's at 1 week past, 1 month future. try lowering it if yours is higher.

I recently upgraded to the new Blackberry Connect Desktop program and the new Nokia PC Sync suite and now have the exact same problem.

The Nokia PC Sync suite does not appear to control the range of appts loaded by Blackberry Connect desktop program. It used to be very slow but it would finish - I loaded some 700+ appointments.

Now with my Nokia 9300, Nokia 9300i and Nokia 9500 I get the same error you outlined.

I'm going to load and try prior version(s) of the Blackberry Connect program on another PC and try to determine which version user to work!

If you or anyone else has gotten the current version to sync via Blackberry connect please post your solution.

I've emailed Nokia but have not gotten a reply yet.

The Nokia PC Sync program works perfect for local sync'ing with my Exchange calendar but that is not what is needed for BlackBerry Calendar set-up.

Thanks - FLG>>>

Just loaded the new BB connect software for my Nokia E61.

After 45 minutes of "calendar extract and load" I rec'd the exact same client error!

FLG>>>