[Techgirl357]

Removed user from Bes server and added user back the user status stay's on Initalizing. All other acitive users are set to running status. I tested it again by removing and adding a test account that had no problem. But once the account was removed and added back to the BES server I get the same status as initalizing.

Please help!!!

[Guy]

What BES version are you using? Is it with Exchange or Domino? Has the user been assigned a handheld by activation?

[belair57]

Got the same problem after installing BES 4.0 SP2 HF 1!
Using Domino 6.5.2 and BlackBerry 7290 with 4.0.2.35.

In another thread i see that someone else has the same problem after installing SP 2 but no fix for that.

Is anyone here can help?

Thank you.

[cdnbeef]

Same problem - using Win2k, Exch. 5.5sp4, BBES 4.0.2.8
Brand new install, but can't get the handheld provisioned (I assume because it's always 'initializing')
Everything else appears correct - CDO.dll, MAPI, etc.

[corey@12mile]

Go into Enterprise Activation from the Options menu and hold down the Alt key and type 'cnfg' without the quotes and there you can disable then re-enable the wireless sync property for Enterprise Activation and it will get the ball rolling again.

cd.

[cdnbeef]

I don't see Enterprise Activation since running Desktop Manager and configuring the Redirector and Intellisync settings.
It still says 'initializing' in Blackberry Manager and I still can't get my Exchange info...

[corey@12mile]

Are you on a BES server?

If you are, go into options on your handheld and remove all the service books dealing with webclient/bwc/bis.
From there go into Enterprise Activation from within options again and do what I said earlier.

If you are not on a BES, connect your handheld to your machine and regenerate the encryption key from the redirector settings (security tab I think). You just basically have to select manual encryption keys and move the mouse around when it says to do so.

cd.

[corey@12mile]

Oh... all this assumes you have OS4 on your handheld, if you don't you really should upgrade.

cd.

[cdnbeef]

Win2K Server, EXCH 5.5sp4, BBES 4.0.2.8
OS4 on BBerry
Trying to deploy from Admin computer...
I will try removing service books and let you know how it goes.
Thanks for all your help.

Do you know a good Deployment Resource for deploying handhelds without installing Desktop Mgr on all desktops?
RIM's documentation is not very clear - they state that this is an option, but they don't tell you how to configure the devices without Desktop Mgr....

Thanks again!

[corey@12mile]

Adding the handhelds to the BES can all be done via wireless activation. Security policy is setup when it's activated. You can use a browser channel push to push URL's containing OTA installs of apps you need, or you can use javaloader from an admin machine with up to 128 devices (max USB devices supported on a single machine) at a time...

MDS Studio is in beta right now, but it has the ability to push complete apps developed in it down to BES users.

If I am not mistaken there are pretty good threads on here about using javaloader. Have a look through and I am sure you will find what you need. I have never really used it for mass rollouts, but I know it has been discussed.

cd.

[T-Roy]

Originally Posted by cdnbeef

Do you know a good Deployment Resource for deploying handhelds without installing Desktop Mgr on all desktops?
RIM's documentation is not very clear - they state that this is an option, but they don't tell you how to configure the devices without Desktop Mgr....

Thanks again!

Your probably reading the wrong guide. Review the deployment section of the Handheld Management Guide.

http://www.blackberry.com/knowledgec...17561&vernum=0

[cdnbeef]

Nope, read that one seven or eight times now.
I guess I just don't see where it loads the information needed to sync with Exchange...never mind that I have other issues just trying to Provision or use Wireless Activation.

[corey@12mile]

I don't think you can really do mass EA using javaloader. I would imagine that if you started the EA wirelessly and then plugged it into the server it would continue via the wire and you could USB hub it to your hearts content. But I think that the loader app is more for installing apps and such as oppsed to EA.

cd.

[cdnbeef]

Thanks to all who responded.
I uninstalled and reinstalled BBES 4.0.2 and it started working immediately. Didn't blow anything away on the server after the uninstall except renamed the Research in Motion folder. Didn't touch SQL MSDE...
As soon as the reinstall was complete, activation was instant.

[MobileRC]

strange. I have seen this problem if you are not logged in as BESAdmin trying to provision

[Team503]

I have the same problem.

Environment:
BES: Win2k3 Srver, BES 4.0.2.8
Exchange: Clustered Win2k3 ES, Exchange 2k3
Handhelds: Various including, 7280 and 7100g, both running 4.0.0.219

I have tried upgrading the 7100g (that's in process as I type this), restarting the individual services as well as bouncing the server.

No matter what happens, adding new users (either remove/re-add or adding users that have never been on the BES) results in the user status sitting at Initializing forever. When running our BES using the DTM, no problems were had communicating with RIMM's servers, and the users were able to send receive. Moving to a centralizing management solution (BES) so we can remove the need to run DTM on each machine was supposed to be easy. Apparently not.

Communications tests with RIMM succeed. We want to use Wireless Enterprise Activation, but the handheld says "Activating...Retrying..." until you cancel it. I suspect this is the result of the "Initializing" status.

Here's the applicable chunk of the log file.

[30068] (10/11 11:59:51):{0x8B8} User starting up...
[30069] (10/11 11:59:51):{0x8B8} {kevin.brown@x.com} Mailbox name is kevin.brown
[40221] (10/11 11:59:51):{0x8B8} {kevin.brown@x.com} In Cradle timer is 653000
[40683] (10/11 11:59:51):{0x1004} {kevin.brown@x.com} Updating the refID generation number
[40684] (10/11 11:59:51):{0x1004} {kevin.brown@x.com} Updating DataSourceId '1f3f23'
[40239] (10/11 11:59:51):{0x1004} {kevin.brown@x.com} Still handled by desktop
[30160] (10/11 11:59:51):{0x1004} {kevin.brown@x.com} GetDeviceId() failed
[40000] (10/11 11:59:51):{0x1004} {kevin.brown@x.com}-HandleDatabaseChange- Failed to read Cal Sync State use previous value=0
[41079] (10/11 11:59:51):{0x1004} PagerImp::SaveChanges: changed items = 51, 52, 53, 59, 65, 75, 76, 77, 84, 86, 87, 88, 89
[40442] (10/11 11:59:52):{0x1004} User settings: email=kevin.brown@x.com, routing=kevin.brown@x.com, service=, device=, calendar=0, MDS=1, userOTAFM=0, incradle=0, SMIME=0, sentItems=0, dir=kevin.brown, server=BMF_CLUSTER
[30000] (10/11 11:59:52):{0x1004} {kevin.brown@x.com} Sending data to Dispatcher, size=91, Tag=108
[40000] (10/11 11:59:52):{0x1004} {kevin.brown@x.com} SendToDispatcher, Tag=108
[40000] (10/11 11:59:52):{0x179C} [BIPP] Send data, Tag=108
[40000] (10/11 11:59:52):{0xF38} [BIPP] Received status DELIVERED, Tag=108
[41079] (10/11 11:59:52):{0x1004} PagerImp::SaveChanges: changed items = 45
[40000] (10/11 11:59:52):{0x1004} {kevin.brown@x.com} UserControl::UpdateMailboxITPolicy - Updating Desktop ITPolicy Information in the user's mailbox.
[40178] (10/11 11:59:52):{0x528} {kevin.brown@x.com} MAPIMailbox::OnNotify - search complete event.
[40239] (10/11 11:59:52):{0x1004} {kevin.brown@x.com} Still handled by desktop
[30160] (10/11 11:59:52):{0x1004} {kevin.brown@x.com} GetDeviceId() failed
[40000] (10/11 11:59:52):{0x1004} {kevin.brown@x.com}-HandleDatabaseChange- Failed to read Cal Sync State use previous value=0
[40442] (10/11 11:59:52):{0x1004} User settings: email=kevin.brown@x.com, routing=kevin.brown@x.com, service=, device=, calendar=0, MDS=1, userOTAFM=0, incradle=0, SMIME=0, sentItems=0, dir=kevin.brown, server=BMF_CLUSTER
[40413] (10/11 11:59:52):{0x4B4} Before optimization: total number of worker threads 1, where 1 non-removable
[40416] (10/11 11:59:52):{0x4B4} Thread pool for session 0x00fd25e8 (BMF_CLUSTER) has 1 threads to serve 1 handhelds
[40417] (10/11 11:59:52):{0x4B4} After optimization: total number of worker threads 1, where 1 non-removable
[40702] (10/11 11:59:52):{0x1004} {kevin.brown@x.com} Starting message rescan
[40178] (10/11 11:59:52):{0x528} {kevin.brown@x.com} MAPIMailbox::OnNotify - search complete event.
[40703] (10/11 11:59:52):{0x1004} {kevin.brown@x.com} Message rescan completed
[30315] (10/11 11:59:52):{0x4B4} {kevin.brown@x.com} Sending data to PIM Connector, size=3
[40279] (10/11 11:59:52):{0x4B4} {kevin.brown@x.com} SubmitToRelaySendQ, Tag=109
[40000] (10/11 11:59:52):{0x179C} [BIPP] Send data, Tag=109
[40748] (10/11 11:59:52):{0x4B4} License total: 20
[30050] (10/11 11:59:52):{0x4B4} All handhelds started

[FlemmingRiis]

look in your spam filter that the activation mail didnt get stuck from rim, if everything else fails try activating the device over usb to rule out bes errors

[Team503]

We're manually setting the WEA password, so the email isn't relevant. Also, the one user I did use the auto-generate for DID receive the email.

We don't want to activate the devices over USB. We *need* the WEA to work. Many of our users are never in the same city as the BES server.

[Team503]

FYI, we got a single device working after matching the software versions. We're updating other devices now.

[BlackBerryLinks]

Originally Posted by Team503

We're manually setting the WEA password, so the email isn't relevant. Also, the one user I did use the auto-generate for DID receive the email.

We don't want to activate the devices over USB. We *need* the WEA to work. Many of our users are never in the same city as the BES server.

External e-mail is important. Even if you set the Enterprise Activation password, there is an email from RIM (external email) sent to the user. The email must be received by the user in his/her inbox without any modification. Then the BES will pick this email and remove it.

So check if the user can receive outsite emails, if no SPAM filter is removing it or changing the mail and that no inbox rules are running. Also sometimes you need to wait some minutes after you have set the password and don't use everytime the same password.

Regards,
Bob Hillesum