Answered by:
StartTime missing in ActiveSync Calendar Event Change

Question
-
In MS-ASCAL, it says "A Sync command response MUST contain one instance of the StartTime element."
However, my activesync client shows that it gets something like this:
<Change>
<ServerId>------------------------------</ServerId>
<ApplicationData>
<calendar:DtStamp>20171021T152339Z</calendar:DtStamp>
</ApplicationData>
</Change>Ghosted properties are only used in Sync requests as far as I understand. Any idea why my client gets something like this? Thanks.
Answers
-
To update the community on this issue, after testing and review of change filtering code, we determined that for Exchange ActiveSync protocol versions >= 12.0, if the DtStamp and/or Attendees have changed, a Sync Change response will contain only the affected elements (i.e. DtStamp or Attendees) and will not include the StartTime element as [MS-ASCAL] 2.2.2.42 states. We will be updating the document to state the correct behavior. Protocol versions <12.0 are not affected.
Thanks,
Tom
- Proposed as answer by Tom JeboMicrosoft employee, Moderator Monday, December 4, 2017 11:39 PM
- Marked as answer by Carson Ip Tuesday, December 5, 2017 5:14 AM
All replies
-
-
Hi Carson,
I will look into this for you. What version of the protocol, client and server are you using?
Best regards,
Tom Jebo
Sr Escalation Engineer
Microsoft Open Specifications Support
- Edited by Tom JeboMicrosoft employee, Moderator Monday, November 27, 2017 7:18 PM added more version requests
-
Looking at the current specification, 3.2.5.3.3 "Omitting Ghosted Properties from a Sync Change Request" says that you need to use the Supported element in the Sync command request in order for subsequent Change elements to include properties that would otherwise be ghosted. Can you show me the command that was issued originally?
Tom
-
-
It is a sync change response. I issued a sync request (the client is kind of read-only) with no special params I think. The server is outlook.office365.com. I'm just trying out some open-source client out there. Protocol version should be 14.1 but I'm not sure if I mentioned that in the request. If not, it may be 16.0.
Off-topic: Is it possible for you to notify your colleagues at outlook.com that their EAS AutoDiscover service has been down for weeks? The Customer Service of outlook.com has no clue of what's happening. -
-
I would still like to see a trace of this if you can provide it. Please include the the request that made the change as well as the sync request and response.
In the meantime, I am still digging to see what conditions might apply to this situation.
Tom
-
-
-
To update the community on this issue, after testing and review of change filtering code, we determined that for Exchange ActiveSync protocol versions >= 12.0, if the DtStamp and/or Attendees have changed, a Sync Change response will contain only the affected elements (i.e. DtStamp or Attendees) and will not include the StartTime element as [MS-ASCAL] 2.2.2.42 states. We will be updating the document to state the correct behavior. Protocol versions <12.0 are not affected.
Thanks,
Tom
- Proposed as answer by Tom JeboMicrosoft employee, Moderator Monday, December 4, 2017 11:39 PM
- Marked as answer by Carson Ip Tuesday, December 5, 2017 5:14 AM