[Tickets #13052] Re: ActiveSync no longer works

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13052
------------------------------------------------------------------------------
  Ticket             | 13052
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | ActiveSync no longer works
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-03-26 19:25) wrote:

> I guess, that the xml might be invalid or "to deep" as only a depth  
> of 32 tags seems to be supported - check line 426 where the  
> assignment takes place and line 81 where the array is declared.
> Another point is - why is the xml not completly logged? Is it  
> invalid in genral or just not logged completly?

There is probably an error or uncaught exception being thrown  
somewhere that stops processing. Check the server error log and/or the  
horde debug log.

Also  wireshark trace will show  exactly what is being sent to the  
client, so that would be useful in figuring out what is wrong with the  
wbxml, though my guess is that some error text is being leaked into  
the wbxml stream.


>
>  DEBUG: [9357] O   <Folders>
>  DEBUG: [9357] O    <Folder>
>  DEBUG: [9357] O     <SyncKey>
>  DEBUG: [9357] O      {53330849-eef8-45ba-9b6a-6e4a4e6f48ba}2
>  DEBUG: [9357] O     </SyncKey>
>  DEBUG: [9357] O     <FolderId>
>  DEBUG: [9357] O      @Calendar@
>  DEBUG: [9357] O     </FolderId>
>  DEBUG: [9357] O     <Status>
>  DEBUG: [9357] O      1
>  DEBUG: [9357] O     </Status>
>  INFO: [9357] Horde_Core_ActiveSync_Driver::getMessage(@Calendar@,  
> 20130525100228.Q9N04N7InFClaWmpHdJ8Vg1 at nnnn)
>