[SullyBES]

Hello everyone,

A few weeks back, I got a new BESEX server up and running, along-side our existing old BES server (which we are working on eliminating). Things have been going smoothly, we've been migrating users over using the transport tool and haven't had any problems (about 40 users done so far).

Now all of a sudden, we are unable to activate new users on the new server, and are getting errors in the event logs for the last batch of users that was transported: Event ID 20400 with OpenMsgStore (0x8004011d) failed followed by a 20154 User Not Started.

IEMSTest gives the same results. I found this thread:
<snipped first part of URL, since I can't post a link-- it is on these forums>250217-help-openmsgstore-failed-8004011d.html
Which was about the same issue, and the resolution was to recreate the MAPI profile being used.

I did that, and immediately after doing that an IEMSTest goes through just fine. Ten minutes later, I am getting the same errors, and IEMSTest on the same user that just passed now fails again with OpenMsgStore.

Any thoughts on where I should be looking into this? I am combing through logs, but an not yet an experienced BES Admin, so I am hoping someone can point me in the right direction!

[SullyBES]

Also, I am not receiving this error message for all users-- just the ones moved with the Transporter tool in the past day, or those that were activated directly on the new BESEX today.

[freakinvibe]

What is your server OS version of the new Blackberry server? AD version? The number of concurrent MAPI calls is limited on newer OS versions (Windows 2008 +)

[knottyrope]

possible your DNS server hit its connection limits as well.

[SullyBES]

New Bes Express server is on Windows 2008 R2. We are currently in the transition from Exchange 2010 SP 1 from Exchange 2003. The besadmin account is on the new exchange 2010 server, most of the users are still on exchange 2003. It definitely seems like it is a "too many connections" issue of some sort. I have verified the throttling policy is set correctly with all of the right attributes being unlimited. If I stop all of the BES Services and run IEMSTest, The mailbox opens successfully (don't receive the OpenMsgStore Failed)

Here are the IEMSTest results:

First, when BES Services are Running:

Test User: Opening message store using
        /o=Corp1/ou=First Administrative Group/cn=Recipients/cn=test.user
        /o=Corp1/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=FN-EX1/cn=Microsoft Private MDB
Test User: OpenMsgStore failed (8004011d)
Test User: CDO Server Name: FN-EX1
Test User: CDO Mailbox DN: /o=Corp1/ou=First Administrative Group/cn=Recipients/cn=test.user
Test User: CDO logon successful
Test User: CDO COM exception: Code = 80040705, WCode = 0505, Code meaning = IDispatch error #1285
    Description = The attempt to log on to the Microsoft Exchange Server computer has failed. [Microsoft Exchange Server
 Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]].
Test User: CDO test failed
Test User: Active Directory permissions test completed successfully
Test User: Initializing EWS Proxy... successful
Test User: Configuring User... failed

And here when BES Services are not Running

Test User: Opening message store using
        /o=Corp1/ou=First Administrative Group/cn=Recipients/cn=test.user
        /o=Corp1/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=FN-EX1/cn=Microsoft Private MDB
Test User: Mailbox opened successfully
Test User: Root Folder opened successfully
Test User: Folder created successfully
Test User: Test folder deleted successfully
Test User: MAPI test completed successfully
Test User: CDO Server Name: FN-EX1
Test User: CDO Mailbox DN: /o=Corp1/ou=First Administrative Group/cn=Recipients/cn=test.user
Test User: CDO logon successful
Test User: CDO COM exception: Code = 80040705, WCode = 0505, Code meaning = IDispatch error #1285
    Description = The attempt to log on to the Microsoft Exchange Server computer has failed. [Microsoft Exchange Server
 Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]].
Test User: CDO test failed
Test User: Active Directory permissions test completed successfully
Test User: Initializing EWS Proxy... successful
Test User: Configuring User... failed

Looking into that CDO COM exception now

[knottyrope]

What version is the CDO.DLL file on BES?

dont tell me 1.2.1, we need the verison in properties when you right click it

[SullyBES]

File Version 6.5.8244.0 for CDO.DLL

I found this in the MAGT log for all of the effected users:
MAPI call failed. Error 'The information store could not be opened.', LowLevelError 0, Component 'MAPI 1.0', Context 649

Searching on that leads me to more posts that seem to indicate it is still a throttling policy error. I recreated the throttling policy, assigned it to the bes user, and rebooted both my exchange 2010 MB and CAS servers, followed by a reboot of my BES Express server. Same result.

[SullyBES]

Okay I think we are getting somewhere now-- On the exchange 2003 machine, I found an event log error indicating the following:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9646
Date: 3/13/2012
Time: 10:44:25 AM
User: N/A
Computer: FN-EX1
Description:
Mapi session "/o=Corp1/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=BES Admin0ab" exceeded the maximum of 32 objects of type "session".


I'm not sure why that was never a problem before with our old BES server (does BES Express do something differently in terms of MAPI sessions, or perhaps it is related to the BES Admin account being moved to exchange 2010?). Anyways, there is a registry setting that I can set to increase the number of MAPI sessions on exchange 2003, but it requires restarting the IS, which I cannot do until tonight. I will test that out and report back.

[knottyrope]

using 2008 Global catalogs?
KB17325-Issues with the BlackBerry Enterprise Server when using a Windows Server 2008 Global Catalog Server - NSPI Bind Limit exceeded

[SullyBES]

Changing the registry setting for Max number of allowed sessions on the exchange 2003 machine, and then restarting the information store seems to have resolved my problem.

Thanks for that link Knotty-- that didn't seem to be the particular error I am having this time, but as I move more users over it may be something I have to look into as well.

Here is a link to the specific KB article from Microsoft, and registry edit, that fixed this for me:

Okay, I still can't post links. KB Article 842022