[Tickets #14177] Re: ActiveSync SQL error

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14177
------------------------------------------------------------------------------
  Ticket             | 14177
  Updated By         | o+horde at immerda.ch
  Summary            | ActiveSync SQL error
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | No Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


o+horde at immerda.ch (2015-12-24 15:31) wrote:

>>> Additionally I found out that the last entry before the error occurs
>>> is the query for the last share in "SELECT * FROM kronolith_sharesng
>>> ORDER BY share_name ASC" (which according to the debug log seems to
>>> be query used by horde-alarms to get the list of shares).
>>
>> By this I wanted to say it seems that the error occurs *after* all
>> shares from kronolith_sharesng have already been processed.
>
> Using the admin phpshell in Horde, look to see what the following  
> produces (using Kronolith's scope):
>
> $kronolith_shares = $injector->getInstance('Kronolith_Shares');
> var_dump(array_keys($kronolith_shares->listAllShares()));
>
> See if there are any "empty-ish" values listed.

Yeah indeed it end with:

   [1451]=>
   int(0)
   [1452]=>
   int(1)

What should we do about them?