[horde] ActiveSync device multiple entries in administration list

[Arjen de Korte]

Citeren Michael J Rubinsky <mrubinsk at horde.org>:

> Quoting Arjen de Korte <arjen+horde at de-korte.org>:
>
>> Citeren "Jens-U. Mozdzen" <jmozdzen at nde.ag>:
>>
>>> Hi list,
>>>
>>> since a few weeks (can't tell when exactly this started) I see  
>>> multiple entries for my Android ActiveSync device in the  
>>> horde/settings/ActiveSync web page  
>>> (horde/services/prefs.php?app=horde&group=activesync).
>>>
>>> When I "reset all devices" (via "reset" button on that page), the  
>>> list is emptied and populated with a single entry after the  
>>> following sync.
>>>
>>> Checking some time later, I found two entries. Today I see three  
>>> of them - and always for the same single device, with identical  
>>> values for "device", "last sync", "status" and the 9 "device  
>>> information" entries (id, key, user agent  
>>> (SAMSUNG-GT-I9595/101.403), model (GT-I9505), IMEI, Common Name  
>>> (jfltexx), OS (Android), OS Language (Deutsch) and EAS version  
>>> (14.1)).
>>>
>>> I noticed this first after seeing problems syncing entries (new  
>>> entries via web didn't sync to the device) after some PEAR update,  
>>> which were fixed by the above "reset" procedure.
>>>
>>> Do others see those multiple entries as well, or is this a unique  
>>> situation here?
>>>
>>> What db table should I check to see if there are actually multiple  
>>> entries, rather than a data access / display problem?
>>
>> That would probably be 'horde_activesync_device' I guess. But I  
>> doubt that it will contain duplicate entries. I tried sync'ing a  
>> single device to multiple accounts and this was refused.
>
> horde_activesync_device and horde_activesync_device and  
> horde_activesync_device_users. Also, syncing multiple user accounts  
> on the same device should be possible. If you are having trouble  
> with it, please create a ticket.

Never mind. It was a problem in the database. I've had some issues  
with updating Horde_ActiveSync a while back which probably broke the  
integrity of the tables. After creating new horde_activesync_* tables  
from scratch, it worked as expected. Apologies for the noise.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5849 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/horde/attachments/20140301/2ceb3c74/attachment.bin>