Hi,
These are some of the methods and success rates in order to get a users BlackBerry phone to start syncing with our exchange server.

- pull battery from unit (20%)
- "resend service books" from server and pull battery from unit (50%)
- delete/re-add user from/to server & wipe unit, rerun enterprise activation (30%)

Eventually, one of the above options works, but it is still bothersome and a rather recent affliction. It only started happening when we switched our service plan from T-Mobile to Sprint, steadily increasing in number over the weeks.

Sprint insists it is a server issue on our side, stating if the user can make and receive calls and browse the web, it is nothing with them. When we had things checked out by RIM, having us check the versions of a pertinent files, they gave it a clean bill of health and stopped short of blaming sprint. Of our 500 users, it seems to affect 2-4 users a day.

The only real change is the amount of users added, which was an extra 200 licenses. Their may have been some firewall changes, but nothing our network admins feel to be a pertinent cause (since 99% of BB users are receiving mail at any given time).

The users afflicted are confirmed to have 1XEV (caps), which should be the best, are not roaming or outside their service network, and have no issues making calls or web browsing. I'm at a loss.

The phones experiencing the issue are all new 8330 and 8350i's. Our server is running BlackBerry Enterprise Server for Microsoft Exchange 4.1.6.