[duarsh]

Hi to All,

Currently i m having a Blackberry server version 4.1.6.21 based on Lotus Domino 6.5.5 running with 160 Users. This server is integrated with 10 Lotus Domino servers in that 9 servers are located at remote locations and connectivity between this is through ADSL line. Now i m getting a problem with address book sync with the users they are in remote server. They are haivng around 3000 to 4000 no of contacts. At the the time of activation if i enabled the address book sync between the Device and server, it is not completing after 4 days also. Kindly give me a solution for this.

[noname]

What is not completing? Enterprise activation or the address book sync?

[duarsh]

Enterprise Activation will complete once all address book entries are transfered. In BB it is showing that 53% or 61%, at server lotus domino console showing that address book entries are transfering. But after two days also the activation is not completing.

[TreeDude]

The 9 remote mails servers are your problem. RIM states that the latency between your mail servers and the BES must be under 35ms. Having 9 of them over a WAN means your latency is way higher than that. You either need to put a BES at each site or pull them all back to a central site.

[DarthBBerry]

During the EA, you can set the Automatic BlackBerry Device Management Enabled = FALSE and Address Book Sync = False. Perform the EA. This will prevent the delay in the Address Book synch during the EA. After it completes, set both back to True. Be sure to also set the Server & Relative Path info.
Server = MailServer/Your Wacky Domain
Relative Path = mail\joeuser.nsf

Finally, resend the service books. You'd be surprise how fast everything syncs when performed this way.

Works for me....

[Aroc]

WE also perform enterprise activations with the "address book sync" set to "false". Then confirm that EA has finished (including message prepopulation) then go back into BES and set it to "true". I have many users with 5000-6000 contacts in the respective address books and staging the EA like this seems to help. These "people" also seem to have HUGE telephone call histories, and these also seem to replicate back to the BES during an EA.