[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 651
  • Last Modified:

Installing Exchange System Manager (ESM) after BES 4.1

Good Morning,

I have been tasked with setting up a BES server for my company. I downloaded BES version 4.1 to be installed on a new machine with Windows Server 03. I also run an SBS03 server which is where exchange is installed and running. After following the instructions provided by RIM for creating the besadmin service account and exchange permission, I am getting the following error in my event logs on the BES server.

{r} MAPIMailbox::MAPIMailbox(2) - OpenMsgStore (0x8004011d) failed, MailboxDN=/o=XXXXX/ou=first administrative group/cn=Recipients/cn=username, ServerDN=/o=XXXXX/ou=first administrative group/cn=Configuration/cn=Servers/cn=XXXXXSBS/cn=Microsoft Private MDB

{username} MAPIMailbox::~MAPIMailbox - DeleteAllDeviceSearches (0x00000000) failed

User username not started

Additionally, I made the mistake of following my friends similar setup which lacked the ESM tools, so I installed and patched them to match Exchange 03 on my SBS server AFTER I did my BES installation.

My question is, do I need to reinstall BES now that the tools are properly installed?
Is my error in line with the mistake I have made, and once I do this reinstall I should be setup correctly, or does this error make you think I have a separate problem?

Thanks for your help in advance.

0
RichAtAvaline
Asked:
RichAtAvaline
1 Solution
 
SysExpertCommented:
I don't know for sure, but I would try the BES uninstall, reinmstall first, and if no go, then start from scratch.

ALSO SBS has all sorts of quirks, so be very careful - see if there is an install DOC just for an SBS environment.


I hope this helps !
0
 
RichAtAvalineAuthor Commented:
Well, apparently the Exchange System Manager issue was irrelevant.

After confirming permissions in Exchange, I checked a level below the first administrative group in the actual store security and it was not inheriting permissions. Once the besadmin account was added to the store for Administer Information Store, Receive As and Send As, the errors cleared up, and we were able to activate and apply a device to a user.

Hopefully this helps someone in the future. Be sure to check permssions are carrying thru the store security as well as the First Admin Group.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now