[Mightypants]

I struggled with the subject with this problem, but here is the problem:

(BES 4.0.2.8, Exchange 2003)

2 new 7230 handhelds still in box. Connected to BES Manager and added the two users. In the BES MAnager it has the user's names, then PIN Number. Obviously, it is intially zero.

Put all the bits together incl sims ad turned on both. Handhelds turn on. Then turn wireless on. Handhelds become GPRS enabled. Connect handhelds to USB cable which is connected to PC with DeskManager 4.0 installed plus new firmware for 7230 handhelds. Asks me to move the mouse around to generate an encryption key. Then the App Loader starts to upgrade the handheld to V4. It finally does this.

I disconnect handhelds from the cable and select Enterprise Activation. The handheld asks for the email address and an activation password which I set myself. The new PIN number is dispalyed on the handheld.

I typed in the email addy and I was half way through typing in the password when the handheld froze. It then unfroze and started the Internet Browser and eventaully came to a sign-up screen which I had never seen before. I wa s able to cancel it and it took me back to where I was. I finished typing in the password and selected Activate. It then did nothing until it said "Retrying.."

I checked the BES and refreshed and there was no PIN bumber in the bES even though there was one on the handheld.

I then wiped the handheld and deleted the BES account and started again. I repeated the same steps but left the cable in after initial connection. It then started doing a desktop activation on it's own and finally registered the PIN on the BES.

It only worked on the cable.

I had setup a 7100 the day before and that worked beautifully, but the next day nothing would work properly with the 7230's. The 7100 regsitered properly and activated wirelessly,

I had a look at the Blackberry logs and found something strange:

[40239] (07/29 10:20:58 ):{0x1E38} {user@domain} Still handled by desktop
[30160] (07/29 10:20:58 ):{0x1E38} {user@domain} GetDeviceId() failed
[40000] (07/29 10:20:58 ):{0x1E38} {user@domain}-HandleDatabaseChange- Failed to read Cal Sync State use previous value=0
[40442] (07/29 10:20:58 ):{0x1E38} User settings: email=user@domain, routing=user@domain, service=, device=, calendar=0, MDS=1, userOTAFM=0, incradle=0, SMIME=0, sentItems=0, dir=USER, server=EXSERVER
\[30000] (07/29 10:20:58 ) :{0x23D8} {user@domain} Sending data to Dispatcher, size=92, Tag=2785
[40000] (07/29 10:20:58 ):{0x23D8} {user@domain} SendToDispatcher, Tag=2785

OK, did we get all that??? Any ideas???

[Rancor]

The device is already active with redirection, and you can not wirelessly activate an active device........
When you are being asked to generate the encryption key, redirection was set up at that stage (redirector?).

Indicated by: [40239] (07/29 10:20:58 ):{0x1E38} {user@domain} Still handled by desktop

Wipe the handheld one more time and restart the Enterprise activation Without connecting to the cable.

[Rancor]

PS:

Originally Posted by Mightypants

Connect handhelds to USB cable which is connected to PC with DeskManager 4.0 installed plus new firmware for 7230 handhelds. Asks me to move the mouse around to generate an encryption key. Then the App Loader starts to upgrade the handheld to V4. It finally does this.

Try using the Handheld Configuration Tool on the BES to upgrade devices instead of the Desktop Manager.

Desktop Manager is OK to use for this purpose BUT should never be run in Online mode to do it.
Force DTM to ask for a profile to use when opening.
When you open DTM and are prompted for profile, select Cancel
That way when you run the Application Loader it will not be trying to also set the device up to an account.

[BB Admin]

I have the exact same problem.

Unfortunately wiping the handheld is not enough.
The problem persists.

Every handheld I try to activate shows the same error in the logs. But if I activate the handheld on a different BES, it works.

It looks like the BES doesn't release the setting and keeps repeating the same error (40239).

Is there a solution except re-installing BES?