BlackBerry Forums Support Community - View Single Post

VinceButler · 12-29-2009, 04:44 PM

Fixed. At least for right now

I just manually assigned permissions at the root of the domain (the same thing I explained in my second post). I still had 32 users who were not starting and were getting the following error:

Event Type: Warning
Event Source: BlackBerry Messaging Agent PUHSD BES Agent 1
Event Category: None
Event ID: 20400
Date: 12/29/2009
Time: 9:24:52 AM
User: N/A
Computer: BES
Description:
{username@puhsd.org} MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed, MailboxDN=/O=PUHSD/OU=District Office/cn=Recipients/cn=username, ServerDN=/o=PUHSD/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CAS01/cn=Microsoft Private MDB

Turns out I never turned off client throttling on Exchange and that was causing the problem. I applied the following command:

Get-ThrottlingPolicy | where {_.IsDefault -eq $true} | Set-ThrottlingPolicy -RCAMaxConcurrency $null

then restarted Exchange, then the BES, and now it looks like things are working normally. I still see some errors in the event log but I think those are related to the user migration from our old BES using the Transporter tool.

12-29-2009, 04:44 PM	#10
VinceButler New Member Join Date: Dec 2009 Model: 8300 PIN: N/A Carrier: Verizon Posts: 7	Fixed. At least for right now I just manually assigned permissions at the root of the domain (the same thing I explained in my second post). I still had 32 users who were not starting and were getting the following error: Event Type: Warning Event Source: BlackBerry Messaging Agent PUHSD BES Agent 1 Event Category: None Event ID: 20400 Date: 12/29/2009 Time: 9:24:52 AM User: N/A Computer: BES Description: {username@puhsd.org} MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed, MailboxDN=/O=PUHSD/OU=District Office/cn=Recipients/cn=username, ServerDN=/o=PUHSD/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CAS01/cn=Microsoft Private MDB Turns out I never turned off client throttling on Exchange and that was causing the problem. I applied the following command: Get-ThrottlingPolicy \| where {_.IsDefault -eq $true} \| Set-ThrottlingPolicy -RCAMaxConcurrency $null then restarted Exchange, then the BES, and now it looks like things are working normally. I still see some errors in the event log but I think those are related to the user migration from our old BES using the Transporter tool.
Offline