SOGo | BTS

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001302SOGoApple iPhone OSpublic2011-05-13 06:542014-09-22 11:03
Reportermark 
Assigned Toludovic 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version1.3.7 
Target Version2.2.9Fixed in Version 
Summary0001302: iPhone 4.3.1 schedule-tag error causes sync failure
DescriptionI haven't pinpointed if this does actually cause the sync failure, or if its just an annoyance/causing free busy issues. I have come across iPhones that needs the account disabling/enabling again after moving to 1.3.7a and this is the only error I can see that might be causing it.

May 12 15:11:07 sogod [381]: [ERROR]
<0x02CD8590[SOGoAppointmentFolder]:user_A_domain_D_net_personal>
DAV property '{urn:ietf:params:xml:ns:caldav}schedule-tag' has no
matching SQL field, response could be incomplete
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
User avatar (0002484)
ludovic (administrator)
2011-05-17 11:12

I've seen that error but no apparent behavior change on the iPhone - everything still work as expected.
(0002489)
mark (reporter)
2011-05-17 12:09

OK - It might have just been my phone had given up and needed a reset after some upgrade to iOS. Can you confirm though, that free/busy scheduling works ok? Does this error indicate something that needs improving in the future?
(0002795)
whroberts (reporter)
2011-08-15 19:29
edited on: 2011-08-15 19:30

I'm seeing this error in my logs too. I cannot get free-busy to work with my iCal clients although it works fine for Lightning and the web interface. This morning I cleaned out my iCal client preferences and then watched the web and SOGo logs when I created the account. As iCal finishes creating the account, it displays "The server where this account is located doesn't allow you to see
availability" in the Account Information tab of the iCal Preferences window. In the Apache access log at the same time I saw this:

150.203.88.124 - - [16/Aug/2011:09:00:15 +1000] "PROPPATCH /SOGo/dav/bill/Calendar/780E-4E27CB00-1-22A69500/ HTTP/1.1" 207 852 "-" "DAVKit/4.0.3 (732.2); CalendarStore/4.0.4 (997.7); iCal/4.0.4 (1395.7); Mac OS X/10.6.8 (10K549)"
150.203.88.124 - - [16/Aug/2011:09:00:15 +1000] "PROPFIND /SOGo/dav/bill/Calendar/personal/ HTTP/1.1" 207 284895 "-" "DAVKit/4.0.3 (732.2); CalendarStore/4.0.4 (997.7); iCal/4.0.4 (1395.7); Mac OS X/10.6.8 (10K549)"
150.203.88.124 - - [16/Aug/2011:09:00:16 +1000] "REPORT /SOGo/dav/bill/Calendar/personal/ HTTP/1.1" 207 744417 "-" "DAVKit/4.0.3 (732.2); CalendarStore/4.0.4 (997.7); iCal/4.0.4 (1395.7); Mac OS X/10.6.8 (10K549)"
150.203.88.124 - - [16/Aug/2011:09:00:16 +1000] "REPORT /SOGo/dav/bill/Calendar/personal/ HTTP/1.1" 207 567879 "-" "DAVKit/4.0.3 (732.2); CalendarStore/4.0.4 (997.7); iCal/4.0.4 (1395.7); Mac OS X/10.6.8 (10K549)"


At the same time in my sogo.log I saw this:

150.203.88.124 - - [16/Aug/2011:09:00:15 GMT] "PROPPATCH /SOGo/dav/bill/Calendar/780E-4E27CB00-1-22A69500/ HTTP/1.1" 207 316/678 0.007 - - 0
150.203.88.124 - - [16/Aug/2011:09:00:16 GMT] "PROPFIND /SOGo/dav/bill/Calendar/personal/ HTTP/1.1" 207 280218/209 0.331 - - 2M
Aug 16 09:00:16 sogod [29745]: [ERROR] <0x08495498[SOGoAppointmentFolder]:personal> DAV property '{urn:ietf:params:xml:ns:caldav}schedule-tag' has no matching SQL field, response could be incomplete
150.203.88.124 - - [16/Aug/2011:09:00:16 GMT] "REPORT /SOGo/dav/bill/Calendar/personal/ HTTP/1.1" 207 737670/35008 0.308 - - 748K
Aug 16 09:00:16 sogod [29745]: [ERROR] <0x084FFD58[SOGoAppointmentFolder]:personal> DAV property '{urn:ietf:params:xml:ns:caldav}schedule-tag' has no matching SQL field, response could be incomplete
150.203.88.124 - - [16/Aug/2011:09:00:16 GMT] "REPORT /SOGo/dav/bill/Calendar/personal/ HTTP/1.1" 207 564753/26086 0.229 - - 552K

I'm running SOGo 1.3.8a and 4.0.4 iCal (latest Snow Leopard).

(0002797)
whroberts (reporter)
2011-08-16 21:38

I've done some more investigating. The schedule-tag error is still occurring, but I don't think it is the cause of my free-busy searches not working in iCal. I had set up the Mac using the Directory Manager to talk to our LDAP server directly for contact lookups. This worked fine for basic lookups, but turns out to be the reason that free-busy was not working. iCal would get the name of a person and then request a bunch of special Apple attributes from the LDAP server (which we don't have) and the free-busy lookup would choke at that point.

I disabled the LDAP stuff, put people in the Address Book ("On My Mac") so that lookups would work and then the free-busy worked.

My fundamental problem was that I was trying to work around a limitation of Address Book.app and iCal (iCal won't look up addresses in shared CardDAV address books configured in AddressBook.app) by using a direct LDAP lookup which was then causing the free-busy search to fail.
User avatar (0007530)
ludovic (administrator)
2014-09-22 11:03

Suspended for now.

First of all, the "has no matching SQL field" can be ignored. They generate no harm.

Secondly, SOGo has received a load of improvements since that bug was filed, and the upcoming v2.2.9 has also tons of improvements for iOS and iCal.

Reopen if necessary by providing new, up-to-date information.

- Issue History
Date Modified Username Field Change
2011-05-13 06:54 mark New Issue
2011-05-17 11:12 ludovic Note Added: 0002484
2011-05-17 12:09 mark Note Added: 0002489
2011-08-15 19:29 whroberts Note Added: 0002795
2011-08-15 19:30 whroberts Note Edited: 0002795
2011-08-16 21:38 whroberts Note Added: 0002797
2014-09-12 11:29 ludovic Target Version => 2.2.9
2014-09-22 11:03 ludovic Note Added: 0007530
2014-09-22 11:03 ludovic Status new => closed
2014-09-22 11:03 ludovic Assigned To => ludovic
2014-09-22 11:03 ludovic Resolution open => suspended


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker