[rehilliard]

Anybody run across an issue with 4.2 on this device as concerns OTA activation?

Spent a couple of hours yesterday with RIM and the device will not activate OTA. Wiped, used Javaloader to wipe, reloaded 4.2 (only "base" apps) and would see activation log messages down to "your email address ..." and then a pop-up error on the handheld to contact sysadmin.

Activating via USB and Destop Mgr worked flawlessly.

Just curious.

Thanks.

[x14]

What's your BES environment?

I had a problem activiating 4.2 devices on my BES 4.1.2 server having a mixed BES 4.1.2/4.1.4 environment.

[rehilliard]

Exch 2k3, single BES 4.0.6.

Although, I'm upgrading to 4.1.4 this very evening.

[mahoward]

I suspect you will see different results after the upgrade. If not, check the MAGT, POLC, and DISP logs to narrow down the issue.

Getting rid of the wireless variable (i.e. doing activation via USB cable) also can clarify the issue. Feel free to post parts of the logs here for assistance.

[hdawg]

If you download the BRK for 4.0.6 there is a tool EAStatus.exe that will comb through the logs and show you where the EA Process stops. Can you get / post those? Also, send over exactly what the HH is displaying on the screen if you can.

[Aroc]

I have no problem with OTA EA using v4.2.1.155 on a 8700c on BES 4.1.4 on Domino 6.5.6FP1.

[rehilliard]

Yesterday, RIM was able to OTA activate a "test" unit running 4.2.1 101 (don't know if it was an 8700c) against the affected mailbox, so that's what's pinning it down to a device issue. The device in question has been activated at least three times in the past on this server (as it is MY device!). The problem unit is running 4.2.1.96 and this is the first time I've tried activating since the hh upgrade 3 weeks ago.

As for the activation log...it gets covered up with the pop-up error very quickly. I'll have to see the log from a successful activation to be able to state it correctly.

Once the upgrade is completed this evening, I'll more than likely wipe and run thru it again just to see what, if anything, happens. I'd forgotten about the RK utility.

If I still had it, I'd reload a previous hh software to pin it down to either a physical "oddity" or an OS issue...

I'll post any new info...or logs if it continues failing.

Thanks for the feedback.