[matthewtrotter]

I have 2x BES 5.0.1 (MR1) servers (BES1,BES2), one has the Exchange 2003 CDO and the other have Exchange 2010 CDO. I only have a single Administration Service and single monitoring instance on BES1.

Everything WAS working fine for about a month and a half and then enterprise activations just stopped working yesterday on BES1

Error 20400 in event log:

{username@mydomain.com} MAPIMailbox::MAPIMailbox - OpenMsgStore (0x80040204) failed, MailboxDN=/o=Organization/ou=First Administrative Group/cn=Recipients/cn=username, ServerDN=/o=Organization/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=ExchangeServer/cn=Microsoft Private MDB

followed by Error 20154 in event log:

"User FirstName LastName not started"

Corresponding Error in MAGT log:

[40720] (03/16 09:30:13.392):{0x1160} MAPI call failed. Error 'An unexpected error has occurred.', LowLevelError 0, Component 'MAPI 1.0', Context 644

If I put the user on BES2, it works and I can activate them, but 2003 users obviously experience issues with their calendars. An attempt to move them to BES1 once successfully on BES2 makes their BB stop working.

If I reboot BES1, magically it starts working again, for a short while (less than a day) and then stops. *UPDATE* Rebooting is NO LONGER fixing the problem - I cannot activate devices on BES1 anymore

FURTHER TESTING - IEMSTest reports back the following:

Opening Default Message Store Mailbox - BESAdmin

FirstName LastName : Opening message store using
/o=UHNResearch/ou=First Administrative Group/cn=Recipients/cn=username
/o=UHNResearch/ou=First Administrative Group/cn=Configuration/cn=Servers
/cn=ExchangeServer/cn=Microsoft Private MDB
FirstName LastName : Mailbox opened successfully
FirstName LastName : Root Folder opened successfully
FirstName LastName : Folder created successfully
FirstName LastName : Test folder deleted successfully
FirstName LastName : MAPI test completed successfully
FirstName LastName : CDO Server Name: ExchangeServer
FirstName LastName : CDO Mailbox DN: /o=UHNResearch/ou=First Admini
strative Group/cn=Recipients/cn=username
FirstName LastName : CDO logon successful
FirstName LastName : Get default calendar folder successful
FirstName LastName : Get calendar folder name successful: 'Calendar
'
FirstName LastName : CDO test completed successfully
FirstName LastName : No Send As permission for the {Domain\bes
admin} account operator.

Notice the last line: Too bad it's not accurate because Send As perms are enabled. If I run this test on a perfectly working user, the same response comes back

Any takers? Because I don't want to have to reboot my P.O.S. BES everytime I want to activate a new user or reactivate a broken one.