End date of (old) reoccuring events isn't effective after migration to Exchange 2010

Bug #870033 reported by Florian Manschwetus on 2011-10-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Exchange Data Provider for Lightning
Undecided
Unassigned

Bug Description

My inbox was moved from exchange 2007 to 2010, now all old (and expired) reoccurring events are active again with no end date set, but in owa and outlook the end date is shown correctly.

Simon Schubert (corecode) wrote :

can you capture a log from one of these events?

Am 07.10.2011 17:08, schrieb Simon Schubert:
> can you capture a log from one of these events?
>
What do you mean with capture? Give me some details on how to do this.

Simon Schubert (corecode) wrote :

See the debugging section on the wiki.

Am 10.10.2011 11:47, schrieb Simon Schubert:
> See the debugging section on the wiki.
>
Hm the log shows correct data:

...
<t:EndDateRecurrence>
   <t:StartDate>2010-04-22+02:00</t:StartDate>
   <t:EndDate>2010-07-16+02:00</t:EndDate>
</t:EndDateRecurrence>
...

Interesting is, server opens messages with:
<h:ServerVersionInfo MajorVersion="14" MinorVersion="1"
MajorBuildNumber="339" MinorBuildNumber="1" Version="Exchange2010_SP1"
xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>

But client with:
<soap:Header>
   <t:RequestServerVersion Version="Exchange2007_SP1"/>
</soap:Header>

As it is tons of output (with personal data in it), please ask a bit
more specific.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers