[jsconyers]

Originally Posted by hdawg

Didn't try that ... however we were able to get the device activated. I don't have an SDR or KB article to point this to, but the solution was:

Close the BES Manager on the BES Server and try the activation. It then succeeded.

I don't get it; its a bug, apparently it has happened before and is being escalated. wacky.

That is odd. I would have never suspected that to be the culprit. Glad to hear you got it activated. I bet the acting CEO is happy now

[hdawg]

Heh, I think hes probably still pissed off that he was without a working device yesterday. He probably would have dumped the BB and demanded a Treo / GMM device if it wasn't working soon enough.

[bencav]

Check with your wireless vendor and make sure that the unit has an Enterprise Wireless Plan as apposed to a Blackberry Internet Plan. According to a Rogers tech I just spoke to, RIM is starting to scan PINs and reconcile the units against accound info that they get from the carriers. If the unit is activated to a BES, but does not have an enterprise plan, RIM disabled the service for that unit without warning.

[hdawg]

The device is a Verizon 8830; Verizon only has 1 type of BlackBerry plan ... all or nothing!

[AlanM]

hdawg, not sure if you did or not, but I would have tried to activate the 8830 on another user. We have a few issues where our 8830s wouldn't activate, but they are mostly due to ESN issues. We have several users that have had the 8703 and now see the 8830 and want to switch. We get the 8830 in and switch the phone number to the new ESN. But what has occurred on a couple of occasions is that RIM holds two ESNs for the number(user). Verizon has had to call RIM and have RIM kick out the old ESN. We find this problem when trying to activate the BB (*22899).

Just something to keep in the back of your head if you are switching out user's BB for new devices.

[Hunter327]

Yeah... this is still an issue. BES is 2 months old and this issue popped up on the 12th user I was attempting to add. Tried 20 different solutions, could activate him once on other devices, but never on the device that was ordered for him. Went back to his original device, added him in the manager, turned off the manager- activated right away.

Enough to drive ya mad.