BlackBerry® Enterprise Service 10

[trbonja]

BES 5.0

BB 9700 with V6 software

User failed to enter correct password and BB got wiped clean.

Attempted associating BB with the same user but no luck - it will not connect with BES - BAS shows policies and service books as Queued.

BB is listed under users profile but no information about device (Home Carrier, phone number...) only PIN.

Re-activation was done using cable attached to PC with BAS

Any suggestions?

Thank you in advance,

T

[knottyrope]

---

trbonja wrote:

BES 5.0

BB 9700 with V6 software

User failed to enter correct password and BB got wiped clean.

Attempted associating BB with the same user but no luck - it will not connect with BES - BAS shows policies and service books as Queued.

BB is listed under users profile but no information about device (Home Carrier, phone number...) only PIN.

Re-activation was done using cable attached to PC with BAS

Any suggestions?

Thank you in advance,

T

---

if its already activaed there is not much more you need to do now.

BAS will not show much info until activation completes.

[trbonja]

Thank you for reply. It's been two days now and still nothing. Usualy when adding users with new BB. it is done within minutes.

I even removed user and recreated user but still no luck.

Regards,

T

[trbonja]

BES alert logs are below:

START==================

30000] (09/18 15:09:32.114):{0x994} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent BESNAME Agent 1 (Application Event Log on BESNAME) | 09/18/2012 15:09:32  (6FFFC3AE) -> [AUDIT] USERNAME@DOMAINNAME.com - User added to the BES
[30000] (09/18 15:09:32.114):{0x618} Alarm::ThreadProc: Received an alarm message
[30000] (09/18 15:30:28.208):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 15:38:43.705):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 15:41:54.491):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 15:57:08.015):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:00:28.207):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:11:23.068):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:17:46.453):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:24:17.838):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:25:34.918):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:30:28.285):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:44:56.166):{0x994} EventLog::ThreadProc: Received notification, processing...
[30000] (09/18 16:49:39.720):{0x994} EventLog::ThreadProc: Received notification, processing...

END===============================

Where is the ThreadProc alarm message stored? Perhaps that will give me some clue what's going on.

As always, thank you for any imput you may have.

T

[knottyrope]

can you provide more of the log please

[trbonja]

Logs are pretty much the same. Re-starting BES server fixed it.
As there is only 40+ users and it take 30 sec for full re-boot (vmware ESX) it's not a bit deal.

Thank you all for replies.

Regards,
T

[knottyrope · Accepted solution]

next time stop the controller, dispatcher and router and start them once all stopped

might save a reboot next time or with VM ware it might be easier to restart