[Tickets #12117] Re: ActiveSync via iOS 6.1.2 for INBOX stops syncing after ERR "Collection does not exist"

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12117
------------------------------------------------------------------------------
  Ticket             | 12117
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            |  ActiveSync via iOS 6.1.2 for INBOX stops syncing after
                     | ERR "Collection does not exist"
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-03-19 13:48) wrote:

> ActiveSync was working for quite some time on my iPhone4 (6.1.2)  
> with "Push" activated in the iPhone settings.
>
> But now the Syncing of my inbox fails after a few dozen of messages.  
> In the log file I can see this:
>
> 2013-03-14T16:06:58+01:00 DEBUG: [26682] Initializing state for  
> collection: INBOX, synckey: {5141e457-bd6c-4454-8b16-6b44c0a8bb01}28
> 2013-03-14T16:06:58+01:00 DEBUG: [26682] Loading state for synckey  
> {5141e457-bd6c-4454-8b16-6b44c0a8bb01}28
> 2013-03-14T16:06:58+01:00 ERR: [26682] Could not find state for  
> synckey {5141e457-bd6c-4454-8b16-6b44c0a8bb01}28.
> 2013-03-14T16:06:58+01:00 ERR: [26682] State gone, PING terminating  
> and forcing a SYNC:
> 2013-03-14T16:06:58+01:00 DEBUG: [26682] Changes available!

I would really need a complete synclog. The first error above is due  
to the fact that the state was dropped from storage - something that  
normally wouldn't happen without either user intervention (explicitly  
clearing the state from the UI) or an infinite sync loop (which is  
detected by the code and causes the state to be forcibly cleared).

Without seeing the earlier entries in the log, it's impossible to  
determine what is going on that initially caused this issue.