none
InvalidPropertyValue in response to SyncFolderItems RRS feed

  • Question

  • One of our customers has an issue synchronizing a Folder with out application (which uses EWS).

    We call SyncFolderItems with BaseShape AllProperties.

    This is the response:

    <m:SyncFolderItemsResponseMessage ResponseClass="Error">
      <m:MessageText>The property has an invalid value.</m:MessageText>
      <m:ResponseCode>
      ErrorCalendarInvalidPropertyValue</m:ResponseCode>
      <m:DescriptiveLinkKey>0</m:DescriptiveLinkKey>
      <m:MessageXml>
        <t:FieldURI FieldURI="calendar:UID" />
      </m:MessageXml>
      <m:SyncState />
      <m:IncludesLastItemInRange>true</m:IncludesLastItemInRange>
    </m:SyncFolderItemsResponseMessage>

    What could cause this issue?

    I suspect that the UID of an appointment is somehow corrupted and the item cannot be delivered via EWS. Is there a way to avoid this? We already have a divide&conquer approach to deal with invalid XML characters in responses, maybe we need to apply that here, too?

    Thursday, October 30, 2014 4:16 PM

All replies

  • Instead of using AllProperties you might want need to use IdOnly and then just add the properties you need to use the other thing you can do is if you know the ItemId use the Ignore element for that particular Item http://msdn.microsoft.com/en-us/library/office/aa563785(v=exchg.150).aspx .

    That should only be a String property so it's surprising that its invalid you could maybe get them to run CalCheck http://www.microsoft.com/en-au/download/details.aspx?id=28786 which should fix any calendar items that are corrupted .

    Cheers
    Glen

    Friday, October 31, 2014 6:38 AM
  • Thank you for your quick reply.

    We'll try the CalCheck tool first. Changing the syncFolder call to IdOnly with additional properties would be an option. I think we use the UID for connecting RecurrenceMasters with their occurrences though, but those are all received with a GetDetails call.

    Currently we do not know which item causes the issue as we were not able to reproduce the issue on our own test system, it occurs only on customer side.

    Friday, October 31, 2014 9:57 AM