[Tickets #11678] Re: ActiveSync missing data in contacts

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11678
------------------------------------------------------------------------------
  Ticket             | 11678
  Updated By         | kd at tu-cottbus.de
  Summary            | ActiveSync missing data in contacts
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
+New Attachment     | log.txt
------------------------------------------------------------------------------


kd at tu-cottbus.de (2012-11-09 17:39) wrote:

ok
started from scratch, sync log attached

>>> 2012-11-09T13:37:31+01:00 ERR: Incrementing counter, we saw this  
>>> synckey before.
>
> This indicates there was error previously in the log. Either the  
> data sent was corrupt, or the device did not receive it/like it.   
> Would need to see the complete sync session to know for sure.
>
> O      <Add>
> O       <ServerEntryId>
> O        20121109131749.wBJmTAx_ywFQnPRtMcKgWYA at www.rz.tu-cottbus.de
> O       <ServerEntryId/>
> O       <Data>
> O        <POOMCONTACTS:FileAs>
> O         King Max
> O        <POOMCONTACTS:FileAs/>
> O        <AirSyncBase:Body>
> O         <AirSyncBase:Type>
> O          1
> O         <AirSyncBase:Type/>
> O         <AirSyncBase:EstimatedDataSize>
> O          0
> O         <AirSyncBase:EstimatedDataSize/>
> O        <AirSyncBase:Body/>
> O       <Data/>
> O      <Add/>
>
> No data for the contact is even being sent to the device, so the  
> error (at least this portion of it) does not lie with ActiveSync. I  
> would check Horde log and/or server error log for any other hints.
>
>
>




kd at tu-cottbus.de (2012-11-09 17:39) uploaded: log.txt

http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=log.txt&ticket=11678&fn=%2Flog.txt