6.0.0-beta1
7/9/25

[#12640] violates unique constraint "horde_active sync_state_pkey"
Summary violates unique constraint "horde_active sync_state_pkey"
Queue Horde Framework Packages
Queue Version Git master
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester michael (at) bigmichi1 (dot) de
Created 08/29/2013 (4332 days ago)
Due
Updated 10/02/2013 (4298 days ago)
Assigned 08/29/2013 (4332 days ago)
Resolved 10/02/2013 (4298 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
10/02/2013 04:58:40 PM Michael Rubinsky State ⇒ No Feedback
 
09/03/2013 04:27:53 PM Michael Rubinsky Comment #6 Reply to this comment
problem is still present with 2.7.3

perhaps i need to mention that this happens only for a android 4.2.2 
device with multiuser support. phones with android 4.2.2 don't log 
this error.
Well, it can't be the exact same thing, because the logice that 
outputs the 110 status code is no longer in the code. Please post a 
new log showing what is going wrong now.

Also, exactly what do you mean by "multi-user support"? Do you have 
two activesync accounts for two different users and this is the only 
time this error happens?
09/03/2013 05:37:54 AM michael (at) bigmichi1 (dot) de Comment #5 Reply to this comment
problem is still present with 2.7.3

perhaps i need to mention that this happens only for a android 4.2.2 
device with multiuser support. phones with android 4.2.2 don't log 
this error.
09/02/2013 08:28:35 PM Michael Rubinsky Comment #4 Reply to this comment
Can you see if my latest changes to git fix this for you?
09/02/2013 05:02:33 PM michael (at) bigmichi1 (dot) de Comment #3
New Attachment: log.txt Download
Reply to this comment
this error occurs every time when the device tries to refresh the inbox folder
08/29/2013 01:54:44 PM Michael Rubinsky Comment #2
State ⇒ Feedback
Reply to this comment
This is expected, and happens when a device does not receive or 
understand the server response to a SYNC request so re-issues the sync 
request. The exception is caught in active sync code and the offending 
key is removed. If this happens often, you should enable the synclog 
and provide a log of the sync when this occurs.
08/29/2013 09:23:43 AM michael (at) bigmichi1 (dot) de Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ violates unique constraint "horde_active sync_state_pkey"
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
i added today some new devices to use active sync and now my log is 
flooded by such messages:

SQL QUERY FAILED: SQLSTATE[23505]: Unique violation: 7 ERROR:   
duplicate key value violates unique constraint "horde_active
sync_state_pkey"
DETAIL:  Key (sync_key)=({521f109b-2678-4563-a524-1914bc286502}2) 
already exists.
         INSERT INTO horde_activesync_state (sync_key, sync_data, sync_devid,
           sync_mod, sync_folderid, sync_user, sync_pending, sync_timestamp)
           VALUES ('{521f109b-2678-4563-a524-1914bc286502}2',
...


i tried to clear all active_sync tables and when all devices trie to 
refresh the messages appear again

Saved Queries