[BBBARW]

I’m currently having some issue with my newly implemented 4.0 BES. Some of the users handhelds are rejecting the default policy, or when they use the enterprise activation the device says that an error occurred and to contact your administrator. Also I have told the server to email me of any problems that may arise and I have been getting a lot of this:

BlackBerry Messaging Agent BHMBB02 Agent 2 (Application Event Log on BHMBB02): 07/26/2005 15:52:25 (AFFF4E21) -> {"user"@"user".com} CalSyncState::OpenStateDB - FindRow(0x8004010f) failed.

BlackBerry Messaging Agent BHMBB02 Agent 2 (Application Event Log on BHMBB02): 07/26/2005 15:52:24 (EFFF2710) -> {"user"@"user".com} PromotePendingAttributes: Promote pending HRT failed

Also, why is it that I can not assign a device to a user wirelessly? Is it because when they sync wirelessly that is the same as assigning that device to some one? I noticed that you cannot do any software configurations wirelessly as well… what’s up with that?

[greywolfe]

Are the handhelds on V4? What email system are you using? What is the version number of the BES?

have you tried activating a user via cable? Does this succeed or throw the same error?

First error looks like a db issue. Are you using SQl or MSDE?

[BBBARW]

All handhelds are 7290's with recent 4.0.2 upgrades from Tmobile. The mail system is Exchange 2003, and BES is 4.0 And no, when I activate or assign handhelds to users I do not receive any errors referring to IT policies

[BBBARW]

This is sloved why my wireless synchs have not been able to go through... check it here RTFM for me But it still does not explain why my database is messing up...

[greywolfe]

So these errors *only* occur when you attempt a wireless activation of a handheld?

[BBTechGuy]

Try doing a security wipe on one of the handhelds and then do another Activation.

[BBBARW]

I have discovered that the errors only show up when the server tries to wirelessly sync. Once the device rejects the “New” IT policy (default Policy) then it starts emailing me these errors. So in order to prove this theory, I wiped a handheld vs. clearing the filing system on one. And wouldn’t know it, the device wireless sync went through with out a problem, and guess what…. No errors on the server as well.

[jibi]

I had this issue when I migrated users that existed within a local BES database to a new remote BES database via Add Users -> Import (the database on the remote server was already inhabited by those from our primary server; I was merging the two databases together).

[BBTechGuy]

With 4.0 you cannot migrate a handheld from one Database to another without first wiping the handheld. The ITPolicy will not apply successfully which will also cause the Wireless Activation to fail.

[jibi]

Originally Posted by BBTechGuy

With 4.0 you cannot migrate a handheld from one Database to another without first wiping the handheld. The ITPolicy will not apply successfully which will also cause the Wireless Activation to fail.

you can easily migrate them from one database to another and have no impact on the user; however, the policy simply won't be applied. wired activation will work fine for this process. i have about 10 users in my local department on our test server that fall under this category simply because they won't do a security wipe.