[Tickets #13338] Re: Activesync: Column 'sync_key' cannot be null

noreply at bugs.horde.org noreply at bugs.horde.org
Fri Jul 11 14:52:36 UTC 2014


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

Ticket URL: http://bugs.horde.org/ticket/13338
------------------------------------------------------------------------------
  Ticket             | 13338
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Activesync: Column 'sync_key' cannot be null
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-07-11 14:52) wrote:

>> Did you update to the latest Horde_ActiveSync package?
>
> Yes, I performed an upgrade of all the packages before trying.
> Looking at this message, it seems the client refuses the new synckey  
> and then Horde tries to save the state anyway with a NULL value for  
> the sync_key

Yes, and that's the exact issue the commit listed in this ticket was  
supposed to fix.

I'll have a look when I'm back at my office.





More information about the bugs mailing list