Article ID: 2295902 - Last Review: February 10, 2011 - Revision: 2.0

An excepted occurrence is not excluded from a recurring iCalendar message for an Exchange Server 2010 mailbox user

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • A Microsoft Exchange Server 2010 mailbox user receives a Simple Mail Transfer Protocol (SMTP) message that contains a recurring iCalendar message part.
  • The recurring iCalendar message part contains an excepted occurrence that is defined by the EXDATE property.
  • The DTSTART property and the EXDATE property are in different time zones.
In this scenario, the occurrence is not excluded from the recurring iCalendar message.

For example, you create the following Recurring Rule (RRULE)-based appointment. The properties in this appointment have the following characteristics:
  • The DTSTART property uses the "Central Europe Standard Time" time zone.
  • The first EXDATE property uses the same time zone as the DTSTART property (through the omission of a specific time zone).
  • The second EXDATE property uses the "Zulu" time zone (denoted by the "Z" suffix).
  • The third EXDATE property uses the "Pacific Standard Time" time zone.
DTSTART;TZID=Central Europe Standard Time:20091212T104700
DTEND;TZID=Central Europe Standard Time:20091212T111700
RRULE:FREQ=MONTHLY;COUNT=15;BYMONTHDAY=12
EXDATE:20100512T104700,20100512T104700
EXDATE:20100612T084700Z,20100612T084700Z
EXDATE;TZID=Pacific Standard Time:20100712T004700,20100912T004700


In this example, when you view the calendar instances from OWA, Outlook 2007, or Outlook 2010, you see that the EXDATE instances in which the DTSTART property and the EXDATE properties are in different time zones are not deleted. However, all the EXDATE instances should be deleted.
Back to the top

CAUSE

This issue occurs because the EXDATE property is not executed when the DTSTART property and the EXDATE property are in different time zones.
Back to the top

RESOLUTION

To resolve this issue, install the following update rollup:
2425179  (http://support.microsoft.com/kb/2425179/ ) Description of Update Rollup 2 for Exchange Server 2010 Service Pack 1
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 EXDATE property, visit the following Microsoft website:
General more information about the EXDATE property (http://msdn.microsoft.com/en-us/library/ee219091(v=EXCHG.80).aspx)
For more information about the DTSTART property, visit the following Microsoft website:
General information about the DTSTART property (http://msdn.microsoft.com/en-us/library/ee158730(v=EXCHG.80).aspx)
Back to the top
APPLIES TO
  • Microsoft Exchange Server 2010 Service Pack 1, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
Back to the top
Keywords: 
kbqfe kbfix kbexpertiseinter kbsurveynew kbhotfixrollup KB2295902
Back to the top