Link to home
Start Free TrialLog in
Avatar of TestMonkey
TestMonkey

asked on

BES 5.0.1 MR1 UGH HELP MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed

So everytime I restart the BES server a new user will get this error message:

MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed

Afterwards it says cannot start user

What annoys me is that its a different user after a restart everytime, never the same ones.  Last night I fixed them all, did a reboot now three are having the issue, before they were the ones i got working without any effort.  They cant do a wireless nor a usb activation

REALLY ANNOYING

ANy help
Avatar of TestMonkey
TestMonkey

ASKER

I FEEL like throwing this thing out and flipping to iPhones
Is this a brand new installation? or did you upgrade from a previous version of BES?

If it happens for random users it could be that the number of MAPI sessions required by BES has been exceeded. This doesn't apply for any accounts that have been granted "View Information Store Status", so try adding that permission to the BESAdmin account contained in the exchange view only admin role.
The BES Admin account has the view only, and exceeded mapi connections?  Where do I check that?

What I need to understand is this.

My own user id in exchange, when i look at the normal permissions and advanced, i dont see anything to do with the BESAdmin user, my username functions perfect, i can activate in anyway i like.

Other users that I have issues with have the BES admin user id under their security and advancd security settings, some inherit the send as function and some i can add or remove.

Yes this was an upgrade
Are those users members of groups that are protected? such as Account Operators?
Check here for a list of protected groups that could potentially have permissions revoked:

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB12309

In your event viewer do you have any events that say "Exceeded maximum objects of type "session""?

{first.last@domain.com} MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed, MailboxDN=/o=Company/ou=First Administrative Group/cn=Recipients/cn=first.last, ServerDN=/o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE/cn=Microsoft Private MDB

Here is the error that keeps showing up, I just did another restart and two different users ended up getting the message above, this is my point i guess, each restart its a different user :P REALLY annoying

I know it sounds like a permission issue but seriously the permissions are all perfectly the same.
Ok heres what even MORE MESSED UP

I have 4 users on a static agent 200, moving them back to 1 they dont work, now i added the three non working to another agent 201 and they work but the users in 200 dont work, adding the same users all to the same group half fail

What on earth is this sh*t
Ok in that error log do you also see after
{first.last@domain.com} MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed, MailboxDN=/o=Company/ou=First Administrative Group/cn=Recipients/cn=first.last, ServerDN=/o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE/cn=Microsoft Private MDB

the following entry: "MAPI call failed. Error 'The information store could not be opened.', LowLevelError 0, Component 'MAPI 1.0', Context 649" ?

Also, in event viewer do you have an error from Source: MSExchangeIS with EventID 9646?

It does sound like there's a bottleneck with the messaging agents making a call into exchange.

Just a side-note too - what's your exchange licensing like? are you licensed per server/cpu? or per seat? I don't think it should make a difference, but perhaps licensing could be the bottleneck? doesn't really make sense as then your outlook clients would fail too. However worth a look too?
outlook clients are not failing just BES users

whats odd is the last message i posted, over 500 enterprise cals and full enterprise edition of exchange 2010
I had a static mailbox agent 200 configured, the users that dont work on the default i move to 200, well some that dont work on either work on a new one i called 201, but i get them working and everyone on 200 fails

Makes zero cents
So it sounds like you're limited to a single messaging agent? by default BES will create up to 4 (or is it 5 now with 5.0?) dynamic agents, so by adding additional it could be causing problems.

Any other errors in the dispatcher (DISP) log, or event viewer?
negative its the only error and seems random to the user
can you try run the handheldcleanup.exe tool on the BES to see if there are any errors with the BESAdmin mailbox? it can be found in program files\research in motion\blackberry enterprise server\tools

run it with the -u switch.
I have an issue with that one :P because i created a mailbox called blackberry server with the space i cant runt he handheldcleaup utility
can you run it as blackberry%20server?
says invalid profile

this time i did another reboot, created a single 200 static mailbox agent, only two users are in it.  ALL users started except one that ALWAYS starts on the 1st mailbox lol

Now one cant connect

this is freaking redicules
Let me guess. If you create another messaging agent and put that one user on it, the rest don't work?
yeap but theres only two message agents

sounds like theres a max connections per user problem here
I did another restart, a different single user cannot connect HA this is so freaking weird
ASKER CERTIFIED SOLUTION
Avatar of TestMonkey
TestMonkey

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Glad it's resolved for you. Thought it must have been something to do with some sort of throughput, mapi or otherwise.
Now I need to figure out how to get that handheldcleanuputility to work with a profile that has a space in it
dang, i should have gave u points for this!@!@

You meantioned an error in event viewer, the error isnt there so I started watching the security logs, blackberry logs in many many many many times.  Did a quick look at the deployment guide and noticed the command, checked and the policy was enabled again.

I think its possible that the policy starts after a reboot
But that's a reboot of exchange not BES, right? the shell command you're running is set on Exchange, not BES.
Yeap its all on exchange

What I tested was rebooting the BES, this time all I did was reboot the exchange, on reconnect a different user would get the boot
Hi, as an FYI by entering the two commands below you will eventually recieve a OpenMsgStore failed (8004011d) error.

New-ThrottlingPolicy BESPolicy
Set-Mailbox "BESAdmin" -ThrottlingPolicy BESPolicy

To correct this issue follow the guide below:

RESOLVED: OpenMsgStore failed (8004011d) error in Exchange 2010
http://www.blackberryforums.com.au/forums/microsoft-exchange/8577-resolved-openmsgstore-failed-8004011d-exchange-2010-a.html