Caldav client configuration

[gren]

If you point a web browser at http://mc.com/api/dav where mc.com is the name for the machine that hosts Scalix Messaging Services what do you see in the browser? Note that you will be asked to login.

If things are working, you should be able to navigate by clicking on links to something that looks like :
http://mc.com/api/dav/Principals/user.name@mc.com

This is a suitable URL for use when adding a new Account in Apple ical.app
Alternatively :
http://mc.com/api/dav/Calendars/Users/u ... m/Calendar

This is a URL that is suitable for Lightning as a CalDAV calendar name.

If things are not working then have a look in the Apache logs or in the tomcat logs in /var/opt/scalix/??/tomcat/logs/ - in particular Catalina.out or scalix-api.log

Regards,
Gren.

[Eugene]

Hi Gren / all

We've had a look in the suggested logs and only found a INFO message "ValidateJarFile(/vara/opt/scalix/cs/tomcat/webapps/caa/WEB-INF/lib/j2ee.jar) - jar not loaded. See Wervlet Spec 2.3, section 9.7.2 offending class: javax/servlet/Servlet.class"

The user is still able to create calendar entries from iCal which shows up in SWA, but when he refreshes the calendar in iCal it still falls over with the HTTP 400 error (same as before).

Any suggestions on where to next?

Best regards,
Eugene

[gren]

The error message about j2ee.jar is not related to this issue (and can be ignored).

You can increase the level of logging for Messaging Services.
See the file :
/var/opt/scalix/??/platform/log4j.properties

I suggest you take a backup of this file so that you can re-instate it later.
Where ever you see "WARN", "ERROR" or "FATAL" in this file, you can replace that word with either "INFO" or "DEBUG".
Then restart tomcat using "service scalix-tomcat stop" and then after half a minute or so, "service scalix-tomcat start".
More information should start being logged to scalix-api.log and scalix-api-activity.log. Depending on your settings, possible dramatically more!

If this still doesn't help then doing a network trace of activity on port 80 (assuming you are using HTTP and not HTTPS) might be useful. HTTP 400 means "Bad Request" which is a bit odd.

Regards,
Gren

[Eugene]

Hi Gren / everyone

We've made the suggested changes to the logging and after trying to refresh the iCal calendar again we did not get any more messages in the logs (than those that appeared to be normal).

We then started to suspect that the iCal refresh request might not even be making it to the server.

We took the Scalix box of the network, tried refreshing the iCal calendar and got the same bad request error as before.

We were using the Scalix machine's IP address in the iCal setup and decided to see whether changing this to a host name would make a difference.

After setting up an entry in the Mac's hosts file for the Scalix box and using the hosts name rather than the IP address all appears to be working like it should.

Thanks again for the help!