I work for a small company who's BES suddenly stopped working. All the services are running under BESadmin, I can start and stop the server and connection service from both Administrator and BESadmin.

When I start it from Administrator I get a message that looks like this:

"Failed to open the default message store using the MAPI Profile 'BlackBerryManager'. Please review the log for details. You will not be able to send messages from BlackBerry Manager by email"

When I open it under BESadmin it does not give me this error.

When I look at the event log it tells me this:

Event Type: Error
Event Source: BlackBerry Messaging Agent FKS-MARS Agent 1
Event Category: None
Event ID: 10277
Date: 2/16/2009
Time: 11:33:36 AM
User: N/A
Computer: FKS-MARS
Description:
BlackBerry Messaging Agent FKS-MARS Agent 1 failed to start. Error code 5302

and:

Event Type: Warning
Event Source: BlackBerry Controller
Event Category: None
Event ID: 20406
Date: 2/16/2009
Time: 11:33:37 AM
User: N/A
Computer: FKS-MARS
Description:
The description for Event ID ( 20406 ) in Source ( BlackBerry Controller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 'FKS-MARS' agent 1: will not restart - reached the maximum of 10 restarts per 24 hours.

I've tried a few fixes I found in threads with similar issues to no avail. This included the KB00075 and a fix related to writing a script to delay the start up of the blackberry services so they don't start at the same time as Exchange.

Any help would be greatly appreciated. Thank You.

If installed on its own box.

log off of administrator and reboot

logon only as besadmin on that box from now on.
let us know if everything started up ok.

If not change log on back to besadmin for those services

Administrator does not have mailbox permissions that are similar to BESAdmin.
That is why it did not work.

Knotty,

Thanks for the suggestion, but it didn't work. We are still not able to get our BBs to receive or send mail.

Exchange and BES are on the same box. I restarted the server and only logged onto BESadmin, started up the server and verified that it was working. Last contact to handhelds was 2/12.

It was working perfectly before this and now does not work, no settings were changed.

Do you have auto updates on?

If so the the new Exchange patch might be installed.

You might have a permissions issue and it need to be changed.

View Document

Did some one remove that user from view in active directory?

make sure your login with BESAdmin and check your services on my computer > right click > manage.

All services BlackBerry as BESAdmin

Yes, I had already checked that.

I've also made sure BESadmin has the propper permissions in AD and in the local computer. I did however notice that Windows Updates did, in fact, run on the same day our BES stopped working.

Thanks for Knotty for suggesting that link with some steps to try. I'll reset all those permissions and report back.

Thank you everyone for your help.

My bes stopped working as well.

yesterday we changed our ISP. i had to change our external ip addresses and now the blackberry will not send or recieve emails ? did i miss something?

Did you change your firewall rule to let out port 3101 for the BES?

I worked through all of those steps and every one was already in there. Everything as it should be. I reselected all the correct permissions and restarted the server. Still no go.

Any other suggestions?

Edit: Are there any known incomaptibilites between SEP ver 11 and BES?

Edit 2: I did not see this warning before:

"Failed to register Service Principal Name for exchangeRFR; error code was c007200e."

http://www.blackberryforums.com.au/f...t-working.html

Post 3 from me...had error 5302 after I recreated the service account.

Try this for error 5302- http://www.blackberryforums.com.au/f...or-5302-a.html

If that doesn't work, try recreating the service account - http://www.blackberryforums.com.au/f...-accounts.html

Also, make sure that you don't hide the BES service account from the address list, ie untick the box in the screenshot!

I have resolved a similar problem yesterday recreating the besadmin mapi profile.

Thank you so much Stix!

I deleted the MAPI profiles in the registry, as per one of your links. *Made a back-up first, of course* Then recreated them. Worked like a charm. I guess the profiles got corrupted somehow when we updated.

Admin can go ahead and close this topic. Thanks everyone!

Good to hear.

Cheers

woot stix