Put this in the wrong forum, so reopened here in admin corner.

So I was having some problems activating with my old server... it was old, and was time to move on up in the world. My organization bought two front end servers for a BES each, and a powerful back end SQL server. I have things looking like things are hooked up, and everything is working properly, until I actually do the testing.

First one is the problem I got the new servers for. When I enterprise activate, it gets hung up on 11%, then nothing. Email actually flows, but never fully activates... Never pulls the handheld info... I can see the PIN on the server, but not handheld version and all that jazz.

Next problem is this:
I also setup a BB Manager on my workstation, so I could provision devices on my workstation, and not go back to the server each time. When I put the devices on, and try to provision them I get this error:

An error occured while assigning the device to the user. The user is not yet know to the Blackberry agent. It can take several minutes for a newly added user to be fully initialized by the server before they can be provisioned. (16).

3. I try activating with desktop manager, and you can synch with your box, but it never actually activates!!!

Help I am running out of time to get this running, monday is my deadline for this!!!

I am running
BES 4.1 (SP2 HF1)
Exchange 2K3 SP2
Win2K3 (SP1)

I called RIM with my Tx2 support, but havent figured it out yet... hoping you all could help me out... its starting to piss me off.

Thanks,

SSgt Adams

An error occured while assigning the device to the user. The user is not yet know to the Blackberry agent. It can take several minutes for a newly added user to be fully initialized by the server before they can be provisioned. (16).

Very familiar error...

You may be assigning a handheld to a user from the BlackBerry Manager on a remote computer that is not part of the same Windows domain as the BlackBerry Enterprise Server.

When using Windows authentication, the configuration database does not authenticate the user logging into the workstation. For example, the local computer cannot be authenticated. Because of this, a new account must be created that is capable of authenticating an account on the BlackBerry Enterprise Server against the configuration database.

Try adding a Windows account on the BlackBerry Enterprise Server with the same login name and password as on the remote administrator’s computer.

On the Activation issue, try removing the user, wipe the handheld and then re-add user and set a new activation password and do it all over again. For troubleshooting activation, take special note on the stage which it does not respond and refer to RIM's KB-05202 Support - Identifying and troubleshooting enterprise activation issues, it is a very detail guide.

Good luck!

Thanks, tried all that, but to no avail. I am using besadmin to log into server, and machine I am using blackberry manager on, to avoid those pitfalls. I am using SQL authentication... utilizing the SA account.

Im pretty lost in this.

Adams

I've had this issue before when trying to assign device directly from the BES, with a new user running MSDE. I think it's something to do with when you add a new user it sometimes takes the BES 5-10 minutes to catchup with itself before you can continue the process.

Also my fallback in the event of total issues with activating devices is wipe the device, install the desktop manager on the end-users computer and wired activate. I know this is in the 'stupd question' category but did you setup DM for BES when you installed it? If DM is not connecting to the BES and giving you the 'generate encrytion key message' then thats pretty unusual, and would suggest you might have a permissions issue on the BESadmin account.

If the DM install is not possible then I stick the device on the back of the BES itself. For me this has cured most issues...

Not sure this adds that much as I guess you've tried all these..

Thanks for your info... I did figure it out. And found the Event ID of all the wireless apps had been changed most like to the information store resize recently. The only fix for these issue unfortunately is to export all mailboxes ot a PST, delete and recreate the boxes, with a import from the PST. This cleared up all issues I was having.

Thanks all.

Adams