BUG: get_StartTime Returns Incorrect Date (296659)



The information in this article applies to:

  • Microsoft Exchange 2000 Conferencing Server
  • Microsoft Exchange 2000 Server

This article was previously published under Q296659

SYMPTOMS

The IConferenceProfile interface that is passed back by the ConfirmScheduleRequest method as pCProfileOld has an incorrect value in the StartTime property.

CAUSE

When there are no preexisting exceptions to the meeting, Conference Server references the wrong meeting instance to construct pCProfileOld. Subsequent changes receive the correct StartTime in pCProfileOld.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Book a recurring meeting; for example, Monday 4/2/2001 through Friday 4/6/2001 at 10:00 A.M.
  2. Change the time of one instance of the meeting, for instance Tuesday 4/3/2001, to 1:00 P.M. This change fires the ConfirmScheduleRequest method, which is passed two pointers to IConferenceProfile: one for the old meeting (pCProfileOld) and one for the new meeting (pCProfileNew).

    StartTime on the new meeting profile is correct, but StartTime on the old meeting profile is incorrect. The date returned will be the next occurrence of the meeting in the list of the recurring meetings. Using the above example, StartTime would return 4/4/2001 at 10:00 A.M. instead of 4/3/2001 at 10:00 A.M.

    This will only occur the first time that you change that specific occurrence; if you try to change that Tuesday again, StartTime will be correct.
This bug affects all recurring meetings regardless of their recurrence pattern.

Modification Type:MinorLast Reviewed:7/15/2004
Keywords:kbbug kbMsg kbpending KB296659