[Tickets #12956] ActiveSync Loop

noreply at bugs.horde.org noreply at bugs.horde.org
Wed Feb 5 13:49:04 UTC 2014


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

Ticket URL: http://bugs.horde.org/ticket/12956
------------------------------------------------------------------------------
  Ticket             | 12956
  Created By         | rbe at tritem.net
  Summary            | ActiveSync Loop
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


rbe at tritem.net (2014-02-05 13:49) wrote:

Hi,

I have new problems with ActiveSync since version 2.12.2 (thanks again  
Michael for solving my previous problem).

My phone under WP8 and with a EAS account is now looping during  
synchronization (Horde_ActiveSync 2.12.3), causing the following  
problems :
- i'm not receiving the new messages
- i can't access the contacts and the maibox on the phone
- no more matching between the contacts and the incoming calls (i only  
see the phone numbers and not the contact names)

I ran an analysis and the problems occurs only AFTER i had accepted a  
meeting invitation on my phone (which is correctly synchronized with  
horde since version 2.12.2).
Accepting the meeting implies the creation of a new message in the  
sent mailbox folder.
After this, the loop is coming during the next synchronizations (not  
sure it is just after).

The found workaround is to move all the messages from my sent folder  
to a archive file (with O2013) and the sync becomes OK (after phone  
reboot and apache restart).

You'll find attached an extract of the sync log.

I believe that the error is becoming from the message :
NOTICE: [26533] Error saving state for synckey  
{52f160f2-b58c-4573-a135-5f0d58bfbacc}5: SQLSTATE[23000]: Integrity\
  constraint violation: 1062 Duplicate entry  
'{52f160f2-b58c-4573-a135-5f0d58bfbacc}5' for key 'PRIMARY' - removing  
previous sync state and t\
rying again.

If you need more information, tell me.

Thanks.

Richard





More information about the bugs mailing list