Hello!

I am at my wits end as to how to resolve this issue. Everytime my BES server starts up, the BlackBerry Messaging Agent fails to start 10 times and then is shut down by the controller.

The message I get is: BlackBerry Messaging Agent <server name> 1 failed to start. Error code 5305

I have followed and eliminated the 11 steps to take outlined in the Blackberry help technote. Expanded my BESADmin account to full admin rights to everything on my system. Yet no success.

Any help on this issue I would be most grateful for, I am desperate!

Thanks

Greg

So this is a somewhat straightforward issue outlined in KB01018 - Service failed to start, generating error 5305.

I'd highly recommend creating a new BES Admin account (assign permissions per: KB02276 - Assigning permissions for a BlackBerry Enterprise Server service account) and then change all the services (while keeping the services stopped)

Login as the new service account make sure you've got a MAPI profile created (KB10285 - How to re-create the BlackBerry Enterprise Server MAPI profile) and then start the services up.

Rather than going through those 13 or so steps again, just start from scratch with a new admin account ... it'll be quicker.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

Thanks for the help. I created a new account, followed all the steps, but still nothing. After all that I am still getting the same error, except this time with the new account.

After reading many many articles regarding resetting if MAPI profiles, editing registry settings, nothing seems to be working.

The only thing I can add is that this installation of BES is on the Exchange server. I know it is not the preferred way to do it, but it is for a pilot project involving only 5 - 7 users so I felt it would be OK. I researched this and found no documentation saying it couldn't be done.

Is there something that I am missing?? My Exchange server is Exchange 2003 sp2, running on Windows 2003 sp2, server is a member server. BES is 5.0.

Any suggestions or help would be very much appreciated.

Thanks.

Greg

Ok, first and foremost BES 5.0 is NOT supported in any way shape or form on the same OS as an Exchange server.

can you copy todays log files to a temp directory, zip them up and email me them (hdawg@port3101.org)? I'll look at em and will post back anything relevant removing anything personally identifiable.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

Hello:

Thanks a million for the simple solution.... get the BES off of the Exchange server. Lesson learned.

I uninstalled the BES, installed on a separate server, everything connected up fine with no issues. I had to wipe my handheld of any old configurations before it would accept an Enterprise Activation from the new server.

So the configuration may not be supported by RIM, I can tell you it doesnt work! Issues experienced.... MAPI, Messaging Agent not starting, possible network name resolution.

All is well now.

Thanks!

GMilne67

Excellento! Glad to hear you're up and rolling

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.