[horde] FW: [sync] Activesync Errors

[Michael J Rubinsky]

Quoting Simon Brereton <simon.brereton at buongiorno.com>:

>> -----Original Message-----
>> From: horde-bounces at lists.horde.org [mailto:horde-
>> bounces at lists.horde.org] On Behalf Of Michael J Rubinsky
>> Quoting Simon Brereton <simon.brereton at buongiorno.com>:
>>
>> >> -----Original Message-----
>> >> From: horde-bounces at lists.horde.org [mailto:horde-
>> >> bounces at lists.horde.org] On Behalf Of Michael J Rubinsky Quoting
>> >> Simon Brereton <simon.brereton at buongiorno.com>:
>> >>
>> >> > Okay - so I exported the address book.  Removed the address
>> book.
>> >> > Created a new one (confirmed by a new share_name in sharesng)
>> and
>> >> > imported the address book.  From Global Preferences, I reset the
>> >> > device.  Rebooted the device, the sync starts.  The calendar is
>> >> fine,
>> >> > the addresses are not there.
>> >> >
>> >> > I grabbed a new device and set up the active sync on there.
>> Same
>> >> problem.
>> >> >
>> >> > So, I really don't know where to go from there.  I know you
>> don't
>> >> want
>> >> > the whole sync log :)
>> >>
>> >> The entire log, containing a complete log from a fresh setup would
>> be
>> >> helpful. You can send it to me directly if you wish. If you do,
>> >> please don't obfuscate the synckeys there's no danger is sharing
>> >> them, and I need to see if they change during requests.
>> >
>> > Log sent to you directly...
>>
>> The log indicates the address book sync fails because it can't find
>> the requested address book.
>
> Well, after staring at for long enough, I arrived at the same conclusion :)
>
>> >> > But if you tell me what part you want, I can send that.  It
>> seems
>> >> I'm
>> >> > still getting the invalid addressbook error..
>> >>
>> >> Look in your prefs datastore and find the value for turba's
>> >> "sync_books" and the "default_dir" prefs.
>> >
>> > Okay - this might be the interesting bit.  I searched for those
>> terms.
>> >
>> > Default_dir turns up here:
>> > pref_uid 			pref_scope 	pref_name 		pref_value
>> > simon at mydomain.net 	turba 	default_dir
>> 	b3790d4757f941chopped
>> >
>> > sync_books turns up here:
>> > pref_uid 			pref_scope 	pref_name 		pref_value
>> > simon at mydomain.net 	turba 	sync_books
>> > 	a:1:{i:0;s:32:"b3790d4757f941chopped";}
>> >
>> > b3790d4757f941chopped turns up in these tables:
>> > 1 match(es) inside table horde_datatree
>> > 5007 match(es) inside table horde_histories
>> > 2 match(es) inside table horde_prefs
>> >
>> > (Can I delete the horde_datatree tables now that H4 doesn't use
>> Datatreee)?
>> >
>> > But turba_sharesng has a different sharename for my address book
>> > (PUXoNFyZnp9Ochopped)..  Can this be the reason?
>>
>> No idea why your prefs are pointing to entries in your DT table. Try
>> revisiting, and resetting your prefs (like I think I suggested
>> before). If your prefs are *still* set to these incorrect values then
>> either you are hard coding and locking them in your prefs.php file,
>> or something else is seriously broken with your install.
>
> I don't believe I've ever hard coded anything in a prefs.php file -  
> either in the H3 install, or this one.  This whole migration away  
> from data-tree has been problematic.  Some users had an issue with  
> the calendar showing up which I had to fix in the DB.  I resolved  
> this by changing the prefs_dir and sync_books entries with the  
> sharesng value.
>
> So, to my other question - I ran all the datatree migration scripts  
> when I installed H4.
>
> /usr/bin/horde-convert-datatree-groups-to-sql
> /usr/bin/horde-convert-datatree-perms-to-sql
> /usr/bin/horde-move-history-out-of-datatree
> /usr/bin/ingo-convert-datatree-shares-to-sql
> /usr/bin/kronolith-convert-datatree-shares-to-sql
> /usr/bin/mnemo-convert-datatree-shares-to-sql
> /usr/bin/nag-convert-datatree-shares-to-sql
> /usr/bin/turba-convert-datatree-shares-to-sql
>
> /usr/bin/horde-db-migrate
>
> If you ask me - and I'm sure you won't, and with good reason - that  
> horde-move-history-out-of-datatree didn't work.

That wouldn't affect your AS issues since you have reset the  
activesync connection on your devices. History is only queried as far  
back as either the last successful sync, or the timestamp of the  
initial pairing.

The only thing I can think of is that the datatree share scripts do  
not update the user prefs - probably because not all prefs backends  
can access other user's settings while logged in as an admin. I  
thought there was a login/upgrade task that took care of this though.  
Maybe that failed, or otherwise did not do what was expected for you.

> Should I run it again?  Now that I've migrated and most issues seem  
> to have been ironed out, can I remove the data-tree?  (I'm hoping  
> that will flush out any remaining issues before I move more users  
> over).

No Horde 4 applications support datatree, and datatree tables are not  
used anywhere except the migration scripts, so whether or not you  
remove them is irrelevant to your issue. You can remove them to save  
space/keep things clean, but I would be sure that you have  
successfully gotten any and all information out of them that you will  
need (or make sure you have a backup of them).

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org