BES with Exchange 2007 - problem with Enterprise Activation
 

I'm using BES 4.1 and MS Exchange 2007. Phone model 9000Bold

I didn't have any problem to activate almost all users except one. I've tried to delete/add user again and again on BES, couple times wipped mobile device, but unsucessfull. I've tried using other SIM card on same device, other devices, but it was alvays same.

after switching off email forwarding (delivery options for user mailbox) Enterprise Activation was sucessfull.

Do you have idea how to use mail forwarding and BES at the same time?

If you've set up the mailbox to forward emails out, then you need to make sure you've selected the option to deliver the messages to both the mailbox and the forwarded address.

BES needs messages in the Exchange mailbox in order to function.

Forwarding address beside "Forward to" has also included "Deliver message to both forwarding address and mailbox".

It was also enabled "Grant this permission to" to the same person where forwarding has ben enabled.

Are you able to connect the device to the BES and assign the device?

Also, have you spoken to your provider whether the device is provisioned correctly?
(It's always the first thing I check)

I'm able to connect mobile device to the BES only if I remove from MS Exchange 2007 delivery options (grant permission and forwarding field) for the user that I want to conect to BES. As long as Delivery options are included in user mailbox account on MS Exchange 2007 Server I'm not able to connect it. On mobile device appears "An error occurred. Please contact your System Administrator".


If I connect user to the BES without switched on delivery options in MS Exchange 2007, and after sucessful activation if I switch it on, then status for that user on BES server is "No PIN"
That user is not able anymore to receive emails on mobile device.

Have you looked in the logs for errors in there?
maybe have a look in the MAGT log.

What happens when you try to send an email from the device after it has been activated?
Is there a red cross or can it send ok?

after trying to send message when "No PIN" appears for this user on BES status there is red cross in mobile mailbox for sent items.


Problem is with account "Joe.Hamster@predator.com". That user shares his mailbox with his assistant "Eve.Hamster@predator.com". She should see his mailbox, change calendar and send messages on behalf of him. When this Delivery option is enabled at MS Exchange 2007 server, BES can not support this user (Joe.Hamster) anymore.

here is part of MAGT log.

[40423] (06/26 16:06:11.385):{0x1080} {Joe.Hamster..at..predator.com} Queuing new mail through notification (external). EntryId=1219
[40724] (06/26 16:06:11.385):{0xDA0} {Joe.Hamster..at..predator.com} Get record key for this MAPI object, EntryId=1219
[40423] (06/26 16:06:11.385):{0x1080} {Eve.Hamster..at..predator.com} Queuing new mail through notification (external). EntryId=1220
[40435] (06/26 16:06:11.385):{0xDA0} {Joe.Hamster..at..predator.com} Queuing new mail through notification. EntryId=1219. Msgs Pending 0
[40724] (06/26 16:06:11.385):{0xA58} {Eve.Hamster..at..predator.com} Get record key for this MAPI object, EntryId=1220
[40435] (06/26 16:06:11.401):{0xA58} {Eve.Hamster..at..predator.com} Queuing new mail through notification. EntryId=1220. Msgs Pending 0
[40282] (06/26 16:06:11.448):{0xDA0} {Joe.Hamster..at..predator.com} Queuing DATA from network..at..etp2003.etp.eu.blackberry.net, Tag=-612510318, EntryId=1219
[40282] (06/26 16:06:11.448):{0xA58} {Eve.Hamster..at..predator.com} Queuing DATA from network..at..etp2003.etp.eu.blackberry.net, Tag=-612510318, EntryId=1220
[30083] (06/26 16:06:11.479):{0xDA0} {Joe.Hamster..at..predator.com} Sent ETP::STATUS to BlackBerry system, Tag=-612510318
[40700] (06/26 16:06:11.479):{0xB10} {Joe.Hamster..at..predator.com} Receiving packet from device, size=502, TransactionId=-148598339, Tag=-612510318, content type=OTAKEYGEN, cmd=0x3
[40000] (06/26 16:06:11.494):{0xB10} {Joe.Hamster..at..predator.com} *** OTAKEYGEN *** receiving KEY_REQUEST, transID = 377138482
[40000] (06/26 16:06:11.494):{0xB10} {Joe.Hamster..at..predator.com} *** OTAKEYGEN *** receiving ACTIVATION request, transID = 377138482
[30000] (06/26 16:06:11.494):{0xB10} {Joe.Hamster..at..predator.com} Sending data to Dispatcher, size=86, Tag=1362
[40000] (06/26 16:06:11.494):{0xB10} {Joe.Hamster..at..predator.com} SendToDispatcher, Tag=1362
[40000] (06/26 16:06:11.494):{0xB10} {Joe.Hamster..at..predator.com} Generating AES256 key
[40000] (06/26 16:06:11.494):{0x1774} [BIPP] Send data, Tag=1362
[40000] (06/26 16:06:11.494):{0x3A8} [BIPP] Received status DELIVERED, Tag=1362
[41079] (06/26 16:06:11.510):{0xB10} {Joe.Hamster..at..predator.com} PagerImp::SaveChanges: changed items = 54, 70, 74, 85 Size = 298
[30083] (06/26 16:06:11.510):{0xA58} {Eve.Hamster..at..predator.com} Sent ETP::STATUS to BlackBerry system, Tag=-612510318
[40700] (06/26 16:06:11.510):{0x1010} {Eve.Hamster..at..predator.com} Receiving packet from device, size=502, TransactionId=-148598339, Tag=-612510318, content type=OTAKEYGEN, cmd=0x3
[40000] (06/26 16:06:11.526):{0x1010} {Eve.Hamster..at..predator.com} *** OTAKEYGEN *** Failed to get password for the ACTIVATION request.
[40000] (06/26 16:06:11.526):{0x1010} {Eve.Hamster..at..predator.com} *** OTAKEYGEN *** sending ABORT_TRANSACTION, transID = 377138482
[40583] (06/26 16:06:11.526):{0x1010} {Eve.Hamster..at..predator.com} Sending packet to device, Size=47, Tag=1363, TransactionId=-901470621
[40279] (06/26 16:06:11.526):{0x1010} {Eve.Hamster..at..predator.com} SubmitToRelaySendQ, Tag=1363
[40279] (06/26 16:06:11.526):{0x1010} {Eve.Hamster..at..predator.com} SubmitToRelaySendQ, Tag=-612510318
[40000] (06/26 16:06:11.526):{0x1774} [BIPP] Send data, Tag=1363
[40000] (06/26 16:06:11.526):{0x1774} [BIPP] Send status DATA_ACCEPTED, Tag=-612510318
[40000] (06/26 16:06:11.526):{0xB10} {Joe.Hamster..at..predator.com} *** OTAKEYGEN *** sending KEY_ACCEPT transID = 377138482
[40583] (06/26 16:06:11.526):{0xB10} {Joe.Hamster..at..predator.com} Sending packet to device, Size=248, Tag=1364, TransactionId=-901458629
[40279] (06/26 16:06:11.526):{0xB10} {Joe.Hamster..at..predator.com} SubmitToRelaySendQ, Tag=1364
[40279] (06/26 16:06:11.526):{0xB10} {Joe.Hamster..at..predator.com} SubmitToRelaySendQ, Tag=-612510318
[40000] (06/26 16:06:11.526):{0x1774} [BIPP] Send data, Tag=1364
[40000] (06/26 16:06:11.526):{0x1774} [BIPP] Send status DATA_ACCEPTED, Tag=-612510318
[40239] (06/26 16:06:11.541):{0xDA0} {Joe.Hamster..at..predator.com} Still handled by desktop
[30160] (06/26 16:06:11.541):{0xDA0} {Joe.Hamster..at..predator.com} GetDeviceId() did not return a PIN, PIN currently is not set for this user.
[41079] (06/26 16:06:11.541):{0xDA0} {Joe.Hamster..at..predator.com} PagerImp::SaveChanges: changed items = 91 Size = 8
[40442] (06/26 16:06:11.541):{0xDA0} User settings: email=Joe.Hamster..at..predator.com, routing=Joe.Hamster..at..predator.com, service=, device=, calendar=1, MDS=1, userOTAFM=0, incradle=0, SMIME=0, sentItems=1, dir=joeh, server=SVJATOVID
[40239] (06/26 16:06:11.541):{0xB10} {Joe.Hamster..at..predator.com} Still handled by desktop
[30160] (06/26 16:06:11.541):{0xB10} {Joe.Hamster..at..predator.com} GetDeviceId() did not return a PIN, PIN currently is not set for this user.
[40442] (06/26 16:06:11.541):{0xB10} User settings: email=Joe.Hamster..at..predator.com, routing=Joe.Hamster..at..predator.com, service=, device=, calendar=1, MDS=1, userOTAFM=0, incradle=0, SMIME=0, sentItems=1, dir=joeh, server=SVJATOVID
[30000] (06/26 16:06:11.541):{0x17F4} {Joe.Hamster..at..predator.com} Sending data to Dispatcher, size=355, Tag=1365
[40000] (06/26 16:06:11.541):{0x17F4} {Joe.Hamster..at..predator.com} SendToDispatcher, Tag=1365
[40000] (06/26 16:06:11.541):{0x1774} [BIPP] Send data, Tag=1365
[40000] (06/26 16:06:11.541):{0x3A8} [BIPP] Received status DELIVERED, Tag=1365
[40000] (06/26 16:06:12.088):{0x3A8} [BIPP] Received status DELIVERED, Tag=1363
[40000] (06/26 16:06:12.354):{0x3A8} [BIPP] Received status DELIVERED, Tag=1364
[40239] (06/26 16:06:39.495):{0x17F4} {Joe.Hamster..at..predator.com} Still handled by desktop
[30160] (06/26 16:06:39.495):{0x17F4} {Joe.Hamster..at..predator.com} GetDeviceId() did not return a PIN, PIN currently is not set for this user.
[40442] (06/26 16:06:39.495):{0x17F4} User settings: email=Joe.Hamster..at..predator.com, routing=Joe.Hamster..at..predator.com, service=, device=, calendar=1, MDS=1, userOTAFM=0, incradle=0, SMIME=0, sentItems=1, dir=joeh, server=SVJATOVID
[40690] (06/26 16:07:00.605):{0xA58} {Eve.Hamster..at..predator.com} Starting message status rescan
[40570] (06/26 16:07:00.621):{0xA58} {Eve.Hamster..at..predator.com} FindAndQueueNewMessageStatusUpdates - Queuing new Message Status Update detected for RefId=-1122481474
[40691] (06/26 16:07:00.621):{0xA58} {Eve.Hamster..at..predator.com} Message status rescan completed
[30247] (06/26 16:07:07.481):{0x19C} Server stats - Msgs: Forwarded 719, Sent 36, Pending 1, Expired 0, Filtered 0
[40000] (06/26 16:07:11.356):{0x3A8} [BIPP] Received datagram, Tag=750
[40000] (06/26 16:07:11.356):{0xDA0} {Vrasidas.Grafakos..at..predator.com} Processed MULTI_STATS from Dispatcher, Tag=750
[40000] (06/26 16:07:30.013):{0x3A8} [BIPP] Received status DELIVERED, Tag=1360

hmmm....normally I would say open the message with a red cross and see what the error message is.

I think this means that it's trying to activate against her account too:

{Eve.Hamster..at..predator.com} Receiving packet from device, size=502, TransactionId=-148598339, Tag=-612510318, content type=OTAKEYGEN, cmd=0x3
[40000] (06/26 16:06:11.526):{0x1010} {Eve.Hamster..at..predator.com} *** OTAKEYGEN *** Failed to get password for the ACTIVATION request.
[40000] (06/26 16:06:11.526):{0x1010} {Eve.Hamster..at..predator.com} *** OTAKEYGEN *** sending ABORT_TRANSACTION, transID = 377138482
[40583] (06/26 16:06:11.526):{0x1010} {

but then this means he hasn't been activated...

[BIPP] Received status DELIVERED, Tag=1364
[40239] (06/26 16:06:39.495):{0x17F4} {Joe.Hamster..at..predator.com} Still handled by desktop
[30160] (06/26 16:06:39.495):{0x17F4} {Joe.Hamster..at..predator.com} GetDeviceId() did not return a PIN, PIN currently is not set for this user.
[40442] (06/26 16:06:39.495):{0x17F4}

That's very odd.

Are there any errors in the event log?

no errors. that's strange, too.
I've tried to find more topics regarding collaborative work on MS Exchange mailboxes and BES... unfortunatelly no one had similar problem.

Huh,

I've tried same process with new user.
After unpacking brand new mobile device (BB 8310) and adding never used SIM card (mobile operater has activated Blackberry services on SIM), phone sucessfully updated Service Book.

I've created new user in MS Exchange 2007 and added mail forwarding to other exchange user. Next step was adding this user in BES. After that I've tried to activate mobile user on BES and receive message "An error occurred. Please contact your System Administrator". Next step was to remove user from BES, then to turn off email forwarding, then added user on BES and enterprise activation on mobile device was sucessful. After that I've activated mail forwarding on MS EXchange and it seems to work okay.

What about the original user "Joe Hamster"?

I've completed enterprise activation for that user without additional delivery options in MS Exchange, and after activation added all necessary Exchange services. It seems to work okay

You need to temporarily remove the forwarding rule, or temporarily disable the account from the bes that the messages are being forwarded to. What it looks like is happening is the activation message comes in for user A, exchange forwards to user B, and the bes gets confused when it sees the same device trying to activate for both users and aborts the activation attempt.