<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>violates unique constraint &quot;horde_active sync_state_pkey&quot;</title> 
  <pubDate>Thu, 09 Apr 2026 22:17:56 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/12640</link> 
  <atom:link rel="self" type="application/rss+xml" title="violates unique constraint &quot;horde_active sync_state_pkey&quot;" href="https://bugs.horde.org/ticket/12640/rss" /> 
  <description>violates unique constraint &quot;horde_active sync_state_pkey&quot;</description> 
 
   
   
  <item> 
   <title>i added today some new devices to use active sync and now my</title> 
   <description>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 &quot;horde_active
sync_state_pkey&quot;
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 (&#039;{521f109b-2678-4563-a524-1914bc286502}2&#039;,
...


i tried to clear all active_sync tables and when all devices trie to refresh the messages appear again</description> 
   <pubDate>Thu, 29 Aug 2013 09:23:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12640#t80476</link> 
  </item> 
   
  <item> 
   <title>This is expected, and happens when a device does not receive</title> 
   <description>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.</description> 
   <pubDate>Thu, 29 Aug 2013 13:54:44 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12640#t80480</link> 
  </item> 
   
  <item> 
   <title>this error occurs every time when the device tries to refres</title> 
   <description>this error occurs every time when the device tries to refresh the inbox folder</description> 
   <pubDate>Mon, 02 Sep 2013 17:02:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12640#t80508</link> 
  </item> 
   
  <item> 
   <title>Can you see if my latest changes to git fix this for you?</title> 
   <description>Can you see if my latest changes to git fix this for you?</description> 
   <pubDate>Mon, 02 Sep 2013 20:28:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12640#t80513</link> 
  </item> 
   
  <item> 
   <title>problem is still present with 2.7.3

perhaps i need to men</title> 
   <description>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&#039;t log this error.</description> 
   <pubDate>Tue, 03 Sep 2013 05:37:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12640#t80517</link> 
  </item> 
   
  <item> 
   <title>&gt; problem is still present with 2.7.3
&gt;
&gt; perhaps i need t</title> 
   <description>&gt; problem is still present with 2.7.3
&gt;
&gt; perhaps i need to mention that this happens only for a android 4.2.2 
&gt; device with multiuser support. phones with android 4.2.2 don&#039;t log 
&gt; this error.

Well, it can&#039;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 &quot;multi-user support&quot;? Do you have two activesync accounts for two different users and this is the only time this error happens?</description> 
   <pubDate>Tue, 03 Sep 2013 16:27:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12640#t80536</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
