[horde] Activesync not working

[Louis-Philippe Allard]

On 2011-09-14, at 10:51 AM, Michael J Rubinsky <mrubinsk at horde.org> wrote:

> 
> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
> 
>> On 2011-09-14, at 10:14 AM, Michael J Rubinsky <mrubinsk at horde.org> wrote:
>>> 
>>> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>>> 
>>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>>> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>>>>> >
>>>>> >> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>> >>>> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>>>>> >>> >
>>>>> >>> >> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>> >>> >>>> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>>>>> >>> >>> >
>>>>> >>> >>> >> Hello,
>>>>> >>> >>> >>
>>>>> >>> >>> >>  My Activesync is still not working.  Actually its getting
>>>>> >>> worst. Just
>>>>> >>> >>> >> upgraded to the latest horde framework with
>>>>> >>> >>> >>
>>>>> >>> >>> >>  "pear upgrade -a -B- c horde" and NO errors whatsoever.
>>>>> >>> ....
>>>>> >>> >
>>>>> >>> > --
>>>>> >>> > Horde mailing list
>>>>> >>> > Frequently Asked Questions: http://horde.org/faq/
>>>>> >>> > To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>>>> >> Bad news... I created a dummy calendar while keeping my normal (buggy?)
>>>>> >> calendar in Kronolith and selected only the dummy calendar for sync with
>>>>> >> mobile devices.  Then I added the account on my iphone and sync'ed the
>>>>> >> calendar.  All went fine at first.  All events that were in the dummy
>>>>> >> calendar were sync'ed on the iphone and vice-versa.  Then over the last
>>>>> >> few days I played around by creating & modifying events on the iphone and
>>>>> >> all have sync'ed to horde until the last two event which got sync'ed to
>>>>> >> horde properly (good dates and times) except it was not created in the
>>>>> >> dummy calendar but the real one...
>>>>> >>
>>>>> >> Sound like AS is confused which calendar to use....
>>>>> >
>>>>> > Yeah, that makes sense. I think we need to tweak the logic that
>>>>> > determines which calendar to send new events to. The AS protocol
>>>>> > technically only supports a single calendar. So, what we do is
>>>>> > combine all the calendars into a single stream and send them to the
>>>>> > device. This allows all the calendars the user owns to be visible and
>>>>> > *editable* on the device, but *new* events will *always* go to the
>>>>> > user's default calendar.
>>>>> >
>>>>> > We probably need to either enforce that the default calendar is
>>>>> > always sync'd or if it's not being sync'd, create new events in the
>>>>> > first calendar listed in the sync pref. I would lean towards the
>>>>> > first option.
>>>>> >
>>>>> >
>>>>> >> I'd like to update the AS log but its over 3.5MB.  Anywhere I can upload it?
>>>>> >
>>>>> > If the only error is creating new events in the default calendar when
>>>>> > that is not being sync'd, then the log is not necessary at this time.
>>>>> >
>>>>> >
>>>>> > --
>>>>> > mike
>>>>> >
>>>>> > The Horde Project (www.horde.org[1])
>>>>> > mrubinsk at horde.org
>>>> Yes,  so far thats the only "glitch".  I also like your idea of the main
>>>> calendar as-default for AS.  To troubleshoot the huge glitch I had with my
>>>> calendar, I am leaning toward the corruption in the import from KDE
>>>> (Kontact).  I would'nt be surprised.... I got rid of Kontact a long time
>>>> ago because it had too may bugs and was too heavy (Akonadi)... Anyways, I
>>>> like your idea of re-creating all events from the so-called buggy calendar
>>>> to a new calendar and use it as a real test bench, after a few weeks, if
>>>> all is still fine, I will migrate this test calendar as final and delete
>>>> the original buggy one.
>>>> 
>>>> What would you do to copy/re-create all events ?  One by one will take me
>>>> hours... :(
>>> 
>>> Ideally, you should find out what is wrong with the imported data, maybe even narrowing it down to specific events. My (completely random) guess is that it is probably something concerning recurring events/exceptions and/or timezones. This way you can either not include those events in the import, or fix the data before import.
>>> 
>>> Otherwise, I don't have any other bright ideas.
>>> 
>>> 
>>> The Horde Project (www.horde.org)
>>> mrubinsk at horde.org
>>> 
>>> --
>>> Horde mailing list
>>> Frequently Asked Questions: http://horde.org/faq/
>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>> 
>> That might be a bad idea but is there a way to retrieve events from a database ?  Here's what I'm thinking:
>> 
>> Create a blank calendar;
>> Import a small amount of events;
>> Try the calendar;
>> If all ok Do the following until problem happens:
>>   export calendar as backup
>>   Import more events;
>>   Test
> 
> This isn't a very good idea, but, the event data is stored in kronolith_events in the database. You would have to duplicate the desired entries, and give them new calendar_id entries that match the share_id (from the share table) of the new calendar.
> 
> There are a number of issues with doing this though:
> 
> * The events will still have the same UID. So, you will have two copies of the same event in two calendars that you are the owner of. This is likely to create issues in various places.
> * The history system will not be notified of the events being added to the new share, so will *never* sync to the device unless you create a new sync account after each batch of imported events.
> * The problem might be caused by the data *on import* from your other PIM app. So, while you might find events that are problematic, you/we won't know *why* - making it harder for us to fix any (potential) import bugs on our end.
> 
> -- 
> mike
> 
> The Horde Project (www.horde.org)
> mrubinsk at horde.org

I agree it will make things more complicated and hellish as they are...

I'll play around tonight and post my findings.
>