The PidLidClipEnd property of a recurring meeting request has an incorrect value in an Exchange Server 2007 environment

Consider the following scenario:

• You send a recurring meeting request to a recipient in a Microsoft Exchange Server 2007 environment.
• The recurrence interval of the recurring meeting request is set to a value that is larger or equal to 25 days. The recurring meeting request has no end date.
• The recipient uses Outlook, Outlook Web App (OWA) or an Exchange Web Services-based application, such as a BlackBerry mobile device to accept the recurring meeting request.

In this scenario, the PidLidClipEnd property of the recurring meeting request has an incorrect value. When this issue occurs, the recurring meeting may not visible on the BlackBerry mobile device of the recipient.

This issue occurs because Exchange Server incorrectly assumes that the recurrence interval is in months. This behavior causes the maximum recurrence period check to fail, and the PidLidClipEnd�property is set incorrectly to the end time of the first occurrence. A BlackBerry mobile device depends on the PidLidClipEnd�property. Therefore, the incorrect property impacts the BlackBerry mobile device synchronization.

To resolve this issue, install the following update rollup:

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

You can use Microsoft Exchange Server MAPI Editor (MFCMAPI) to verify the properties.

For more information about MFCMAPI, visit the following Microsoft website:
For more information about the PidLidClipEnd property, visit the following Microsoft website: