If its just a few users, try that method I sent you. Its more complicated that in looks. Also for sanities sake, ensure that in the contacts section on the BB wireless sync is set to yes.
-----Original Message----- From: Benjamin Zachary - Lists [mailto:li...@levelfive.us] Sent: Monday, October 05, 2009 6:54 PM To: NT System Admin Issues Subject: RE: BES 4.1 syncing Thanks all for the tip. I will try the remove/add of the contact on the device. Both my bes problems are small 3-4 users. I know at one its all of them on the 2007 but on the other its just 1. -----Original Message----- From: Jeremy Anderson [mailto:jer...@mapiadmin.net] Sent: Monday, October 05, 2009 9:35 PM To: NT System Admin Issues Subject: RE: BES 4.1 syncing For what its worth.... I have seen that exact issue before, at 2 different clients. The bad news is, I don't know the fix. In one case I synced the contacts using desktop manager The other was not my client and they reinstalled BES (WTF?) -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Monday, October 05, 2009 6:30 PM To: NT System Admin Issues Subject: Re: BES 4.1 syncing On Mon, Oct 5, 2009 at 8:54 PM, Benjamin Zachary - Lists <li...@levelfive.us> wrote: > I have a couple of sites where contacts don't seem to be syncing properly. For all users on the server? That's odd. I've had various cases where a given user will have trouble, but not everyone. Granted, there are only 11 users on our BES, but still. > I tried everything but removing and re-adding the device. I would indeed try removing and re-adding the device -- or more precisely, the user. When BB Manager asks if you want to delete the BlackBerry info, say "Yes". Then re-add the user and reactivate the device. This is really harmless -- no user data should be lost from either server mailbox or handheld. It only discards server metadata and other "behind the scenes" stuff. (But remember, backups are *always* a good idea.) We're running BES 4.mumble against Exchange 2003. Behavior may be different against other mail servers. > Anything else I could try? Before you do anything else, check the logs. Both Windows Event Spewer and the BES text logs. BES logs *gobs* of debug information to the text logs. This will often at least point out that there is a problem, even if you don't know how to fix it. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
