[BCAdmin]

Alright guys, this is my first post to this forum, although I've been digging through posts for several days now to find an answer to my problem.

My company has decided to implement a BES, and we're using BES 5.0 trial. I have also installed the two available MRs. Everything should be happy and shiny, but no. I cannot activate even one device wirelessly.

- I have verified with my provider that the test device is provisioned for BES.
- I do have all of the required permissions for my BESAdmin account, and IEMSTest runs through perfectly.
- I recieve the appropriate .DAT file from the device, which BES promptly picks up....

After that? Nothing. All of the error messages I have seen lead back to either permissions or provisioning, which is why I'm a bit lost here. Any ideas gurus?

Thanks in advance for all your help.
Brandon

We're using Exchange 2003. Sorry.

[DarthBBerry]

Domino? Exchange? Groovywize?

[BCAdmin]

Here is the text from the latest BES_MAGT_ file. Names have been altered.

{user@domain.com} Sending data to Dispatcher, size=367, Tag=145
{user@domain.com} SendToDispatcher, Tag=145
[BIPP] Send data, Tag=145
[BIPP] Received status DELIVERED, Tag=145
{user@domain.com} PagerImp::SaveChanges: changed items = 70 Size = 0
{user@domain.com} *** OTAKEYGEN *** receiving KEY_REQUEST, transID = 330438986
{user@domain.com} *** OTAKEYGEN *** receiving ACTIVATION request, transID = 330438986
{user@domain.com} Sending data to Dispatcher, size=363, Tag=146
{user@domain.com} SendToDispatcher, Tag=146
{user@domain.com} *** OTAKEYGEN *** Generating AES256 key
[BIPP] Send data, Tag=146
{user@domain.com} PagerImp::SaveChanges: changed items = 70 Size = 25
{user@domain.com} *** OTAKEYGEN *** sending KEY_ACCEPT transID = 330438986
{user@domain.com} Sending packet to device, Size=252, Tag=147, TransactionId=-893228225
{user@domain.com} SubmitToRelaySendQ, Tag=147
{user@domain.com} SubmitToRelaySendQ, Tag=-1038324808
[BIPP] Send data, Tag=147
[BIPP] Send status DATA_ACCEPTED, Tag=-1038324808
[BIPP] Received status DELIVERED, Tag=146
{user@domain.com} Still handled by desktop
{user@domain.com} GetDeviceId() did not return a PIN, PIN currently is not set for this user.
User settings: email=user@domain.com, routing=user@domain.com, service=,device=, calendar=1, MDS=1, userOTAFM=0, incradle=0, SMIME=0, sentItems=1, dir=help, server=EXCHANGE (session : 0x016c2830)
BIPP] Received status CANCELLED, Tag=144

[BCAdmin]

Exchange 2003; went and edited it in the original post too... thanks!

[wren]

i assume since you are now implementing a BES that your users were/are using BIS. make sure that you have notified your carrier that you need enterprise data plans, and tell them to make sure to do whatever it is they do on their side, that the devices will be using BES moving forward.

if that's not the issue, what i would do next is start tracking the .dat file from BES to BESAdmin to user back to BES and see where the breakdown is...

[freakinvibe]

I think the problem is

"Still handled by desktop"

in your log. Check out this forum post:

http://www.blackberryforums.com/bes-...tml#post949776

[BCAdmin]

Alright. This one is finally solved. Sounds crazy, but it had nothing to do with permissions, carriers, or BES settings. It was as simple as mismatched SRP ID. It took three RIM techs to find it, but for whatever reason, the SRP ID I was issued did not register to their infrastructure, which caused the communication problem. So for you other folks who are pulling your hair out over this problem, try this solution. (First, double check and make sure that you've input the correct SRP ID (with no trailing spaces or extra characters)). You can check your SRP ID with Blackberry Administration Service.
Go to:
BlackBerry Solution topology
-->BlackBerry Domain
---->Server view
------>(BES Name)
-------->(BES Name - Under BAS)

You can there edit the instance of BES that is having trouble. Hope that this helps some other newbies like me!
- Brandon