[mbr99]

Hi there,

I've seen lots of articles regarding this error. Most of them are with Exchange 2003 and 2007. I'm dealing with a Windows 2008 server with Exchange 2010. The installation of BES was done in 2010. Since then no problems with syncing mail and calendar items.

On the 1st of november we've installed SP1 for Windows 2008. Reboot of the server was done a week later, on the 8th. Since the 3rd I noticed errors in the application log of Windows with eventid 20216. So i'm not sure if the installation of the SP has something to do with this problem. The date of the cdo.dll is 5-4-2010 and is located in the program files (x86)\ExchangeMapi folder.

I've checked the Send As permission for the Besadmin on the useraccounts, it's fine.

Again mail is fine. Only calendar items both ways. All services started. All users with diff BB phone's have the same problem.

What could be wrong?
Thanks.

[freakinvibe]

What are the symptoms? Calendar items are not syncing at all both ways?

[mbr99]

Yes. Correct. Creating items on both Outlook and the BB will not sync anymore.

BTW in the logs i also found this:

[30000] (11/15 09:23:04.704):{0x88C} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent MAILSERVER Agent 1 (Application Event Log on MAILSERVER) | 11/15/2011 09:23:04 (AFFF4EF8) -> {mailaddress@company.com} Synchronize() failed: ERR_FAIL, Tag=307920

I also wonder if it is correct this I only found one CDO.DLL in the earlier mentioned directory. Is this the correct location?

[freakinvibe]

Use the IEMSTest utility and paste the results here. For details see:

KB02091-How to use the IEMSTest.exe tool to verify that the BlackBerry Enterprise Server service account can access user mailboxes

[mbr99]

I seem to have problems running this tool. When starting it asks me for the profile. 2 profiles where set bot none of them seem to work. I'm logged in as domain\besadmin. I created a new profile, verified it so the underline under the username besadmin appeared, but again, a failure:

C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\Utility>iemstest.exe

BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Version 1.0
OpenMsgStore() for this profile failed (8004011d)

[freakinvibe]

You should choose the Profile called

BlackBerryServer

0x8004011d means "The server is not available", so I don't think it is a permissions issue. For some reason it doesn't find your Exchange server. Try to re-create the MAPI profile according to these instructions:

KB10285-How to recreate the BlackBerry Enterprise Server MAPI profile

[mbr99]

Removed regkeys for the profiles and recreated it with succes.

Still, same error when choosing this profile from iemstest.

[freakinvibe]

Have you done the throttling policies as per:

KB20608-Random BlackBerry smartphones fail to start and "MAPIMailbox - OpenMsgStore (0x8004011d) failed" appears in BlackBerry Messaging Agent and Application logs due to Microsoft Exchange 2010 Throttling Policy

[mbr99]

I started in this article below to verify the policy:

[PS] C:\Windows\system32>Get-Mailbox "besadmin" | fl Name,ThrottlingPolicy

Name             : besadmin
ThrottlingPolicy : BESPolicy

[PS] C:\Windows\system32>Get-ThrottlingPolicy | Where-Object {$_.IsDefault -eq "True"} | FL Identity

Identity : DefaultThrottlingPolicy_30e5fc93-419b-4c82-9e53-b52ac4782cbc

Then ...

RunspaceId                     : 96d125e0-9fa5-4c54-9b99-0d5623f1a02a
IsDefault                      : False
EASMaxConcurrency              : 10
EASPercentTimeInAD             :
EASPercentTimeInCAS            :
EASPercentTimeInMailboxRPC     :
EWSMaxConcurrency              : 10
EWSPercentTimeInAD             :
EWSPercentTimeInCAS            :
EWSPercentTimeInMailboxRPC     :
EWSMaxSubscriptions            :
EWSFastSearchTimeoutInSeconds  : 60
EWSFindCountLimit              :
IMAPMaxConcurrency             :
IMAPPercentTimeInAD            :
IMAPPercentTimeInCAS           :
IMAPPercentTimeInMailboxRPC    :
OWAMaxConcurrency              : 5
OWAPercentTimeInAD             :
OWAPercentTimeInCAS            :
OWAPercentTimeInMailboxRPC     :
POPMaxConcurrency              : 20
POPPercentTimeInAD             :
POPPercentTimeInCAS            :
POPPercentTimeInMailboxRPC     :
PowerShellMaxConcurrency       : 18
PowerShellMaxCmdlets           :
PowerShellMaxCmdletsTimePeriod :
ExchangeMaxCmdlets             :
PowerShellMaxCmdletQueueDepth  :
RCAMaxConcurrency              : 20
RCAPercentTimeInAD             :
RCAPercentTimeInCAS            :
RCAPercentTimeInMailboxRPC     :
MessageRateLimit               :
RecipientRateLimit             :
ForwardeeLimit                 :
CPUStartPercent                : 75
AdminDisplayName               :
ExchangeVersion                : 0.10 (14.0.100.0)
Name                           : BESPolicy
DistinguishedName              : CN=BESPolicy,CN=Global Settings,CN=Kantoor Mail,CN=Microsoft Exchange,CN=Services,CN=C
                                 onfiguration,DC=kantoor,DC=nl
Identity                       : BESPolicy
Guid                           : 499f3ed8-c464-4ad7-a01d-e7566feb0522
ObjectCategory                 : kantoor.nl/Configuration/Schema/ms-Exch-Throttling-Policy
ObjectClass                    : {top, msExchGenericPolicy, msExchThrottlingPolicy}
WhenChanged                    : 1-10-2010 9:55:12
WhenCreated                    : 1-10-2010 9:55:12
WhenChangedUTC                 : 1-10-2010 7:55:12
WhenCreatedUTC                 : 1-10-2010 7:55:12
OrganizationId                 :
OriginatingServer              : MAILSERVER.kantoor.nl
IsValid                        : True

In this poplicy not all fields are blank as described. But should the guid be the same as the DefaultThrottlingPolicy nr mentioned above? So am I looking at the right policy then?

[mbr99]

Hi freakinvibe. Are you able to help me further?

[MisterGriffiths]

Shouldn't the EWSMaxConcurrency be NULL?

[mbr99]

@MisterGriffiths: and there are some other settings that should be null. The only thing I'm doubting about is, am I looking at the correct policy before I change these settings as described in the throthling document.

[MisterGriffiths]

I'd perhaps consider starting from scratch. Unassign BESAdmin from BESPolicy, delete BESPolicy and then recreate BES Policy again as per the document.

[mbr99]

As the document described, the default throthling policy is not the besadmin policy, so changing the policy should be safe.

I've performed this via the shell:"

1.On the Microsoft Exchange Server, click Start > Microsoft Exchange Server 2010 > Exchange Management Shell. 
2.Type Set-ThrottlingPolicy BESPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null
3.Type Set-Mailbox "BESAdmin" -ThrottlingPolicy BESPolicy. 
4.Restart the BlackBerry Controller Service.

I'll wait as described in the document and try the iemstest later on.

Thanks for now.

[MisterGriffiths]

Are you running Exchange 2010 SP1?

[mbr99]

No without SP1.

[MisterGriffiths]

Good stuff. Do report back and let us know how you get on.

[mbr99]

OK good news. The last change in the settings of the besadmin profile made me running the iemstest, i finaly could select mailboxes.

This is the output:

Opening Default Message Store Mailbox - besadmin

USERNAME: Opening message store using
/o=Kantoor Mail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=USERNAME
/o=Kantoor Mail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MAILSERVER/cn=Microsoft Private MDB
USERNAME: Mailbox opened successfully
USERNAME: Root Folder opened successfully
USERNAME: Folder created successfully
USERNAME: Test folder deleted successfully
USERNAME: MAPI test completed successfully
USERNAME: CDO Server Name: MAILSERVER
USERNAME: CDO Mailbox DN: /o=Kantoor Mail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=USERNAME
USERNAME: CDO logon successful
USERNAME: Get default calendar folder successful
USERNAME: Get calendar folder name successful: 'Agenda'
USERNAME: CDO test completed successfully
USERNAME: Active Directory permissions test completed successfully
USERNAME: Initializing EWS Proxy... successful
USERNAME: Configuring User... successful
USERNAME: EWS calendar find request... failed

What i see in the forums is that there are 2 ways for syncing calendars, cdo and ews. Since cde reports no failure, should the problem be solved since again i changed the besadmin profile?

What also sounds good is that error 20216 did not appear anymore in the eventlogs since this change.

I'm in the meanwhile waiting for output of users with a blackberry since I myself own a iPhone.

[freakinvibe]

USERNAME: EWS calendar find request... failed

This is normal behaviour if you don't use EWS, so nothing to worry about.

[mbr99]

OK thanks. I will wait for user input now.