BlackBerry Mailbox Agent will not start

[charles_cho]

Hello -

Just installed ZimbraBES connector & we seem to have issues on wireless activation.

1) Running Zimbra NE 5.0.2 on Linux RHE 4.0
2) Widows 2003 SP2 Server running BES 4.1.4.16
3) Installed CDO, Outlook 2003 SP3

Everything looks okay, but the Event Viewer on the BES shows:

MailboxManager::SubsystemInitialize - MAPILogonEx (0x80040111) &
BlackBerry Messaging Agent BES Agent 1 failed to start. Error code 5302

Per my research, this usually refers to the Send As access rights when using Exchange Server (hence make changes to AD).
On Zimbra, the profile I created is an Administrator Account, what else do I need to do?
attached is the Log file from ZimbraBES

[mlanner]

Having very similar problems. Also see this thread:

ZCS NE 5.0.1 Blackberry support

My BB log looks like this:

[30054] (02/25 11:34:17.968):{0xB90} Starting Message System
[30055] (02/25 11:34:17.968):{0xB90} Using MAPI profile BlackBerryServer
[30036] (02/25 11:34:18.000):{0xB90} MailboxManager::SubsystemInitialize - OpenProfileSection[Global] (0x8004010f)
[40206] (02/25 11:34:18.000):{0xB90} MailboxManager::SubsystemInitialize - Using MAPI profile 'BlackBerryServer'
[50000] (02/25 11:34:18.093):{0x1294} Controller: This BES Agent is under control of BlackBerry Agent Controller
[20137] (02/25 11:34:18.109):{0xB90} MailboxManager::SubsystemInitialize - g_pSession->OpenMsgStore (0x8004011d)
[30036] (02/25 11:34:18.109):{0xB90} MailboxManager::SubsystemInitialize - OpenProfileSection[Global] (0x8004010f)
[40206] (02/25 11:34:18.109):{0xB90} MailboxManager::SubsystemInitialize - Using MAPI profile 'BlackBerryServer'
[20137] (02/25 11:34:18.125):{0xB90} MailboxManager::SubsystemInitialize - g_pSession->OpenMsgStore (0x8004011d)
[10277] (02/25 11:34:18.125):{0xB90} BlackBerry Messaging Agent MLA-BES Agent 1 failed to start. Error code 5305
[50106] (02/25 11:34:18.125):{0xB90} Stopping BlackBerry Mailbox Agent 1 for Server MLA-BES
[40507] (02/25 11:34:19.093):{0x1294} ExtUDPLogThread: Code on closing = 0
[30000] (02/25 11:34:19.093):{0x1294} [DIAG] EVENT=Unregister_thread, THREADID=0x1294, THREADNAME="ExtUDPLogThread"
[30065] (02/25 11:34:19.093):{0xB90} BlackBerry Mailbox Agent 1 for Server MLA-BES shutdown complete

Aside from this I'm also getting some warnings in my Windows app log, like:

{StartNotifyThreadServer}: DBNS component not installed.

and

The description for Event ID ( 45058 ) in Source ( DevMgmtConnector ) 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: {StartNotifyThreadServer}: DBNS component not installed..

[mlanner]

Never mind ... I scrapped my BB installation and started over again, reinstalling it all. It now works. Don't know what I did differently, but something made it click.

[charles_cho]

I have reinstalled everything, it worked for a week, and got same messages on the Event Viewer on BES.
Stopped sync with Calendar, then now contacts & emails are down too.

Not going to reinstall it again as I would like to find out where the problem is. One thing for sure is that the ZCB is very unstable...

[alee]

Originally Posted by charles_cho

I have reinstalled everything, it worked for a week, and got same messages on the Event Viewer on BES.
Stopped sync with Calendar, then now contacts & emails are down too.

Not going to reinstall it again as I would like to find out where the problem is. One thing for sure is that the ZCB is very unstable...

Have you tried restarting the agent before reinstalling the product? are the BES services all behaving well? i.e. all starting?
can you post some agent logs?

There is a known issue with calendar sync having problems and we are trying to resolve those. Right now, a restart of the server should do the trick.
For contacts and mail...if those aren't showing up, then there is a deeper issue here. we would need logs to try to figure out what is going wrong with your environment.

--tony