I am in the midst of an upgrade. BES 4.1 running on a Win2000 DC with SQL on a seperate 2000 member server. Exchange 2003 running on a 2000 DC. Everything worked great. I just added a new win2003 member server with exchange 2003 on it. I have moved all mailboxes from the old server over to the new mailserver acept for the BB users. I tried moving some BB users to the new exchange server. As long as the BESadmin accounts mailbox belongs to the old mailserver, the users that got moved to the new server do not get any calendar or contacts sync. They do get email back and forth though. I created a new mapi besadmin account with its mailbox on the new server and plugged that into the mapi profile on my BES and it did not like that at all. When I try to start the Blackberry manager I get the following popup.

Failed to open the default message store using the mapi profile Blackberry Manager. You will not be able to send messages fromBlackberry manager by email. I then get error messages about the Mailbox agent will not start in the app event log. I also get lots of event ID 20406's. It speaks of the Blackberry Controller. It says " The local computer may not have the nessasary registry information or DLL files to display messages from remote computer, The following information is part of the event VHC2 (thats my server) Agent 1 will not restart. It has reached the maximum of 10 restarts in a 24 hour period.

email will not work in either direction, nor will the calendar or contacts. If I move the mailbox of the besadmin account back to the old server, everything starts working again. The deal is, I want to get rid of the old server. It is on its last leg and will not last much longer. I was told that this should be a real easy thing to do, I hope I am just missing some small detail.

BTW: I have the exchange server fully patched, but do not have the BES patched fully. It is just 4.1 with no hot fix on it yet. I have also followed the steps for granting the send as and recieve as permissions for the besadmin account. My besadmin account does not belong to the admins group. It only has logon locally permission to the BES server.

Have you configured the permissions correctly for the BES Admin account on the new Exchange Server.
Send As
Receive As
Adminster Information Store

Also did you say you moved the BESAdmin mail box to the new Exchange or did you create a new Service Account on the new Exchange?

I am fairly certain that I have the permissions set correctly. I have messed with this so much in the last 3 days that I had dreams about it last night. If I go into the Exchange system manager and select the correct server from "1st administrative group>>servers" I added the besadmin account and gave it "Send As, Recieve As and Administer Information Store". There were no deny" permissions selected. The besadmin is only a member of "domain users". The BES Server is now just a member server. I demoted it. The besadmin account is a member of the local admin group for the bes server. It also has the right to "Logon as a Service".

To answer your last question, I moved the besadmin account mailbox to the new server. I also tried creating a new besadmin account from the new server. I gave it all the permissions that the other account had and still no luck.


Thank you for helping me.

Follow RIM KB-04293 Step by step.
Create a new AD user ,exactly as mentioned in the KB,don't miss on any steps.

Btw: Just to check , you definitely have the BESAdmin account as the View Only Admin (Role)

If your BESAdmin account is a member of domain admins then the permissions will get reset after about two hours. I seen a link to a Microsoft KB article a couple of days ago on this forum.

Agent 1 will not restart. It has reached the maximum of 10 restarts in a 24 hour period

Did not notice the above earlier,it seems your server is crashing.
THe controller restarts the BES services if there are too many hing threads or exceptions.

Your problem may be different than what we have ben thinking,check you Messaging Agent logs (MAGT1)

Dropping the Profiles keys and re-creating the MAPI profile for the BESAdmin may do the trick

HKCU>Software>Microsoft>Windows NT>Current Version>Windows Messaging Subsystem>Profile (Drop the keys) Export/Back it up before you do that


The open Blackberry Server Configuration Tool>Blackberry Server Tab

Click on Edit MAPI> Enter BESADmin information

Make sure it resolves properly

(Do a small test here instead of using the Exchang Server name use the GC name to resolve the BES Admin name)

Now Reboot the BES Server

Make sure all BES services start and are logged on a BESAdmin account (Service acount)