Enterprise Activation will not Advance!!! Help!!

[Hatea_Hurta]

Recently had my network admin recreate my domain account because I was unable to reply to emails via my BES due to me being a power user. I imported my profile from my old Outlook to the new. I then wiped my Storm, deleted myself as a user in BES and attempted to activate Enterprise. It gets to the point where it reads "xxx@XXXX.com" is now enabled..... and stops.

I can receive/send emails, view my calendar, but no contacts.

Now note that my old account is still active under zxxxxx.

My network admin says that the profile can take up to 24hrs to build. Not sure if this may be the reason, but it has now reached that point of hour 24 and no change.

Any suggestions?

[aaronjudze0806]

Your password also expires and your admin may need to reset it.

[Hatea_Hurta]

I am the BES admin. I have cancelled the activation and reset my own wireless password and still no luck.

[Slashdpc]

Sounds like your address book database isn't accessible by the BES. In your account in BAS/Blackberry Manager, I'd redo the fields that have to do with address book sync, click ok, then watch the BES console to see if it gives you any errors.

As for "up to 24 hours," that was just your net admin getting you off his ***.

[GlenB]

There is no 24 hour delay in BES. There could be in AD if you have a number of sites and replication only occurs within a given time window each day.

I would start again. Wipe the device and remove the user from the BES. Run the handheldcleanup utility from a command line (c:\program files\research in motion\blackberry enterprise server\utility) with the "-u" switch. Select Blackberry Server as the MAPI profile and then type the BES server name. Then add the user back onto the BES, set the activation password and try activating again.

[Hatea_Hurta]

Thanks for the help guys, but I found what the issue was.

The "BlackBerry Synchronization" service had stopped for some reason. Once I started it back up, I was then able to activate successfully.

Didn't dawn on me until we attempted to activate a new user.

Thanks!