[nf0jxn]

Our new ATT bold has an issue with duplicating the addresses. We are using a BES, the inotes client shows the correct list of addresses, but I don't know where this duplication is coming from. Wireless activation was used and the wireless sync is turned on. Both the notes client address book and the inotes address book only shows the single entries.. Any ideas? Does the BES keep a list of the addresses on it?

[x14]

Originally Posted by nf0jxn

Our new ATT bold has an issue with duplicating the addresses. We are using a BES, the inotes client shows the correct list of addresses, but I don't know where this duplication is coming from. Wireless activation was used and the wireless sync is turned on. Both the notes client address book and the inotes address book only shows the single entries.. Any ideas? Does the BES keep a list of the addresses on it?

Did the BlackBerry already have contact information on it?

You normally see this when you perform an EA and the BlackBerry already have contact information. If the contact in the iNotes is correct and is what you want then wipe the BlackBerry and perform an EA.

[Jadey]

OP, I have moved your post (and x14's reply) to a new thread, as this is not technically the same "problem" as the thread that you posted in.

[DarthBBerry]

I've had this happen on a few devices. There will probably be 2 Desktop entries under the Options for Contacts. One will have Wireless Synch: ON with zero entries and the other will have Wireless Synch: Not Available with a bunch of entries.

My Resolution: Use Desktop Manager to backup the address book only. Wipe the device. Remove the user from BES and readd. Be sure to enter the Server and Relative path info for the PIM settings. Restore the address book only to the device. Perform EA. It should work just fine after that with Wireless Synch: Yes and a bunch of entries. No dupes either.

Good luck.

[bbnotes]

This issue with two "Desktop" entries under the address book appears to have only started with the 4.5 software. Has RIM acknowledged this issue? It is pretty prevalent and the wipe/reactivate solution is not ideal.

[buluks]

as i know, this issue can happen when there is something migration domain, and then the BES push again desktop services to user BES existing.

you can try what darthBBerry say to fix the problem.