07-19-2011 11:08 AM
We just started upgrading all our phones to the latest operating system 188.8.131.522. About 60 % of the phones hang on actication to the BES server. What we see is it will stop at some percentage (53% or close ) and just sit there for ever.
When I have the users cancel the activation, there is often a prompt in the background that says something to the effect "the changes made require the device to be restarted, you have x number of attempts, blaa blaa"
I'm thinking that this message is the problem. If we wipe the phone and activate again, it works fine.
Working with BES 4.1.7 for MDS applications
Here is the complete scenario
1. Phone is activated to BES with 184.108.40.2065 OS. It has security and application policy applied
2. Phone is wiped
3. New 220.127.116.112 operating system is installed via blackberry desktop manager
4. The BES account is removed from the BES server and a new account is created
5. When complete the phone is activated again
At that point the phone either activates correctly or hangs up.
I'm not really looking for advice on this one, just trying to let someone know there is an issue with .522 unless someone see's something glaringly wrong with what I'm doing.
I'm rockin the BlackBerry DTEK60, Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook,BT Headset HS-700
07-19-2011 12:07 PM
why are you wiping the phone? just run loader.exe and after a mini activation will run.
I upgraded my torch yester day with out issue.
might be MDS version of BES, but I have not used it yet.
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V
07-19-2011 12:19 PM
Good question, and it made me think. 1. I didn't know that 2. I'm pretty sure my policy doesn't allow OTA upgrades so I was thinking they couldn't upgrade the phone at all. I actually think I had this happen on a few phones and didn't even realize it. I'll check that out and see if it works for us.