Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Installing Exchange System Manager (ESM) after BES 4.1

Posted on 2008-10-10
2
621 Views
Last Modified: 2012-05-05
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
Comment
Question by:RichAtAvaline
2 Comments
 
LVL 63

Expert Comment

by:SysExpert
ID: 22689799
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
 

Accepted Solution

by:
RichAtAvaline earned 0 total points
ID: 22703586
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

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question