Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Email message delivery is delayed on a Blackberry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install Update Rollup 4 for Microsoft Exchange Server 2010 SP2 in an environment that is running against a Blackberry Enterprise Server (BES).
  • The BES uses MAPI or Collaborative Data Objects (CDO), instead of Exchange Web Services (EWS), to communicate with Exchange servers.
  • The mailbox contains many folders. For example, the mailbox contains more than 5000 folders.
In this scenario, you encounter one or more of the following issues:
  • Email message delivery to the mailbox on a BlackBerry mobile device is delayed.
  • It takes a longer time to complete a folder hierarchy scan in the mailbox. For example, before Update Rollup 4 for Exchange Server 2010 SP2 was installed, a scan that typically takes 5 minutes may now take 30 minutes to 1 hour.
  • The Microsoft Exchange Information Store process (store.exe) on the Exchange Mailbox server may use excessive CPU resources.
  • Some BES event log entries are logged on the Exchange Mailbox server. Before Update Rollup 4 for Exchange Server 2010 SP2 was installed, these entries are less in occurrence or nonexistent.
  • Some events are logged in the BlackBerry Messaging Agent (MAGT) log. These events that are logged in the BlackBerry MAGT log resemble the "Busy Working" threads that are described in the following article in the BlackBerry Knowledge Base: Users may experience delayed email after upgrading to Microsoft Exchange 2010 SP2 Rollup 4 or Microsoft Exchange 2010 SP2 Rollup 5

↑ Back to the top


Cause

This issue occurs because the Exchange server creates a new admin session every time that the�server tries to bind the delegate to each folder and retrieve folder properties for the delegate. Additionally, because the server sets a certain flag for each folder bind, a high-cost process flow occurs. Therefore, when BES requests the properties of many folders, the issue that is described in this article occurs.

↑ Back to the top


Resolution

To resolve this issue, install Exchange Server 2010 Service Pack 3 (SP3) on the Exchange Server 2010 servers. For more information about Exchange Server 2010 SP3, click the following article number to view the article in the Microsoft Knowledge Base:

2803727 Description of Update Rollup 1 for Exchange Server 2010 Service Pack 3

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about the issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:
2726897 Admin sessions are exhausted as a result of delegate access in an Exchange Server 2010 environment
2706690 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.


↑ Back to the top


Keywords: KB2797529, kbfix, kbqfe, kbexpertiseinter, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2797529
Revision : 8
Created on : 8/20/2013
Published on : 8/20/2013
Exists online : False
Views : 294