[Toro34]

Hey all,
I ave searched and searched and could not find an answer.
im having a few issues trying to get an 8900 to sync with my company BES.

The activation email gets sent to the inbox, disappears and i get the progress on the device. But the only item under the Synchronizing Service Desktop is Calendar.

Calendar initalizes, completes and then the BB stays on the screen and the Service Desktop window says *Empty*

The device receives email, but does not sync contacts, tasks, or memos.

Any ideas?

[Toro34]

i forgot to add that the Enterprise Activation icon stays on the BB's desktop and never gives a percentage when activating

[dev]

If this is a new activation for the user, then do the following in the exact order:
1. Remove the user from the BES - do not save BES info for the user
2. Wipe the device - ensure ate & time is correct and wireless radio is back on
3. Add user to the BES
4. Activate user on the device

Sounds like the service books may be corrupted or some of the folders (Address book, calendar) failed to initialize properly. Sometime toggling (setting wireless sync to "False" and "True" again) the settings on the BES server for the specific user kick starts the process. Go to the properties of the user on the BES and check the "PIM Sync" section. Ensure all the entries say "True". If they are, then try toggling them and restarting the Sync service on the BES server as well. Once things start working you'll see initilazation entries in the BES logs (MAGT).

[Toro34]

Hi Dev,
I have tried what you suggested numerous times. I have also tried with different IT Policies. I remember before the Memos PIM sync was causing an issue, and that was the only item i set to false, I will give the others a try and get back to you.

[Toro34]

Ok, an update on the issue.

I noticed it began happening to a couple other Blackberries that I tried to activate.
After logging into BES, i saw that it had been running for 287 days so i got approval to bounce the machine.

Upon restarting, all activations functioned normally. This still leaves me wondering what the cause of the issue was, but at least it is working (for now)