BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 04-01-2008, 10:11 AM   #1 (permalink)
New Member
 
Join Date: Apr 2008
Model: 8100
PIN: N/A
Carrier: Vodafone
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Moving users to a new BES...

Please Login to Remove!

We have recently built a new BES 4.1.4 and are trying to migrate the users from 4.1.3 on different hardware, and a new SQL database.

We are having problems when it comes to activating the devices on the new server. For the most part, they sit on activating until eventually timing out.

The process we are using is as follows:
Wipe existing handheld
Remove User from Old BES and clear all information
Wait +-30mins
Add user to New BES
Set Activation Password
Activate

During activation, the user notices the etp.dat email in their inbox, but it is not deleted as is supposed to happen, and the activation never takes place.

I cannot find anything in the MATG logs or Event Viewer that suggests an error message. Sometimes the activation will eventually work on the 3rd or 4th attempt, but never first time.

Strange thing is if we revert the user to the old bes, it will activate again first time every time.

For the few users that we have managed to activate on the new BES, normal operation is fine, which suggests permissions are all set correctly.

Is there something specifically I should be looking for in the logs to suggest what the problem is?
Offline  
Old 04-01-2008, 10:20 AM   #2 (permalink)
BlackBerry Extraordinaire
 
Join Date: Mar 2007
Model: Z10
OS: 10.1.0.19
Carrier: Fido
Posts: 1,068
Post Thanks: 6
Thanked 30 Times in 29 Posts
Default

how about wired activation?
Offline  
Old 04-01-2008, 12:47 PM   #3 (permalink)
New Member
 
Join Date: Apr 2008
Model: 8830
PIN: N/A
Carrier: Verizon
Posts: 6
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

When we moved we had a similar error. It took us basically starting from scratch and not using any of the old information. It was a huge pain the in @ss but it was much faster in then end.

Don't know if this is something that you want to do or not but thought I would throw it out there.
Offline  
Old 04-02-2008, 01:41 AM   #4 (permalink)
New Member
 
Join Date: Apr 2008
Model: 8100
PIN: N/A
Carrier: Vodafone
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

When we try over the wite activation we get something along the lines of: The user is not yet known to the BES. Please wait a few minutes and try again. We have waited up to a day and get the same message.

Charles can you be a bit more specific? I think thats what we are doing. We have a new BES with a new SQL server on new hardware. The only common thing is the users.

My theory is that there is some legacy information being retained on the old BES that is preventing the new BES from activating the user, but cannot find anything!! We are selecting remove all info when removing from old BES, and I have tried dbclean from the users' machines.
Offline  
Old 04-02-2008, 07:08 AM   #5 (permalink)
BlackBerry Extraordinaire
 
Join Date: Mar 2007
Model: Z10
OS: 10.1.0.19
Carrier: Fido
Posts: 1,068
Post Thanks: 6
Thanked 30 Times in 29 Posts
Default

How about activation an old user with brand new device? Or device that was nuked?
Offline  
Old 04-03-2008, 09:32 AM   #6 (permalink)
New Member
 
Join Date: Apr 2008
Model: 8100
PIN: N/A
Carrier: Vodafone
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Tired Old USer with new device over the cable and get user is nto yet known to the blackberry dispatcher. Tried new user with new device and get same error.
Offline  
Old 04-03-2008, 09:34 AM   #7 (permalink)
BlackBerry Extraordinaire
 
Join Date: Mar 2007
Model: Z10
OS: 10.1.0.19
Carrier: Fido
Posts: 1,068
Post Thanks: 6
Thanked 30 Times in 29 Posts
Default

Are you using new SRP and auth. key on new server?
Offline  
Old 04-04-2008, 02:31 AM   #8 (permalink)
New Member
 
Join Date: Apr 2008
Model: 8100
PIN: N/A
Carrier: Vodafone
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yes we are.

Attempting to connect to :
srp.eu.blackberry.net (193.109.81.33), port 3101
Successful

SRP Key and ID are valid.

Seems fine. The few devices that we have managed to activate are working perfectly fine.
Offline  
Old 04-04-2008, 02:40 AM   #9 (permalink)
New Member
 
Join Date: Apr 2008
Model: 8100
PIN: N/A
Carrier: Vodafone
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Interesting I just found this in the log:

[30000] (04/04 08:28:14.273):{0x7E0} EventLog::ThreadProc: Received notification, processing...
[30000] (04/04 08:28:14.273):{0x7E0} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Dispatcher INXS90090 (Application Event Log on INXS90090) | 04/04/2008 08:28:14 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
[30000] (04/04 08:28:14.273):{0x7AC} Alarm::ThreadProc: Received an alarm message
[30000] (04/04 08:28:20.695):{0x7E0} EventLog::ThreadProc: Received notification, processing...
[30000] (04/04 08:28:20.695):{0x7E0} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Dispatcher INXS90090 (Application Event Log on INXS90090) | 04/04/2008 08:28:15 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
[30000] (04/04 08:28:20.695):{0x7AC} Alarm::ThreadProc: Received an alarm message
[30000] (04/04 08:29:01.259):{0x7E0} EventLog::ThreadProc: Received notification, processing...
[30000] (04/04 08:29:01.259):{0x7E0} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Dispatcher INXS90090 (Application Event Log on INXS90090) | 04/04/2008 08:29:01 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
[30000] (04/04 08:29:01.259):{0x7AC} Alarm::ThreadProc: Received an alarm message
[30000] (04/04 08:29:09.697):{0x7E0} EventLog::ThreadProc: Received notification, processing...
[30000] (04/04 08:29:09.697):{0x7E0} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Dispatcher INXS90090 (Application Event Log on INXS90090) | 04/04/2008 08:29:02 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
[30000] (04/04 08:29:09.697):{0x7AC} Alarm::ThreadProc: Received an alarm message
[30000] (04/04 08:30:15.825):{0x7E0} EventLog::ThreadProc: Received notification, processing...
[30000] (04/04 08:30:15.825):{0x7E0} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Dispatcher INXS90090 (Application Event Log on INXS90090) | 04/04/2008 08:30:15 (6FFFC3B1) -> [SRP] Dispatcher\SRP Connection dropped, Error=0
[30000] (04/04 08:30:15.825):{0x7AC} Alarm::ThreadProc: Received an alarm message
[30000] (04/04 08:30:23.700):{0x7E0} EventLog::ThreadProc: Received notification, processing...
[30000] (04/04 08:30:23.700):{0x7E0} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Dispatcher INXS90090 (Application Event Log on INXS90090) | 04/04/2008 08:30:17 (6FFFC3B0) -> [SRP] Dispatcher\SRP Connection established
[30000] (04/04 08:30:23.700):{0x7AC} Alarm::ThreadProc: Received an alarm message
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.