Article ID: 2658613 - View products that this article applies to.
Consider the following scenario. A user uses Microsoft Outlook, Outlook Web Access (OWA), or a Microsoft Exchange Web Services-based application, such as a BlackBerry mobile device, to accept a recurring meeting request in a Microsoft Exchange Server 2007 environment. The recurring meeting has no end date. In this scenario, the PidLidClipEnd property of the recurring meeting request is not set to 31 August 4500, 11:59 P.M. as expected. In this scenario, the BlackBerry mobile device is not synchronized with the calendar items in the mailbox.
For example, the user uses a BlackBerry mobile device to join a recurring meeting. However, the recurring meeting is not visible on the BlackBerry mobile device.
This issue occurs because BlackBerry mobile devices depend on the PidLidClipEnd property to synchronize the calendar items. The PidLidClipEnd property of the recurring meeting request is incorrectly set to 12/31/4500, and the incorrect property disrupts the BlackBerry mobile device’s synchronization.
To resolve this issue, install the following cumulative update:
(http://support.microsoft.com/kb/2608656/ )Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3
For more information about the PidLidClipEnd canonical property, visit the following Microsoft website:
General information about the PidLidClipEnd canonical propertyFor more information about how to use Microsoft Exchange Server MAPI Editor (MFCMAPI) to verify the PidLidClipEnd properties, visit the following Microsoft website:
How to use MFCMAPI to verify the PidLidClipEnd propertiesFor more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2598980/ )The PidLidClipEnd property of a recurring meeting request has an incorrect value in an Exchange Server 2007 environment
Article ID: 2658613 - Last Review: February 13, 2012 - Revision: 2.0