JSCalendarSync debugging tips


Some of you have had some issues when starting JSCalendarSync. Some of these issues were due to bugs in my code, some other due to some kind of corruption in the local sync database on your mac.

I would like to thank all of you who reported errors and suggested enhancements, all the fixes and some enhancements are already ready in CVS and will be shipped in the next release.

In order to help to debug any issue, I often ask you to turn debugging on, here is a set of instructions to do this.

Turn JSCalendarSync’s debug mode on

  • Ensure the application is not running,
  • Open a Terminal and type
    defaults write com.sun.luxembourg.cso.JSCalendarSync debug -bool true
  • Open the application again and use it normally (i.e. start a sync session – only modified events if possible to limit the amount of data writen in the log file)
  • Be sure to quit JSCalendarSync to flush the log
  • Send me by email the file located at
    Home Folder -> Library -> Logs -> JSCalendarSync.log
    (this file does not contain any sensitive data such as password, but it contains the adress of your calendar server and your username. You might want to strip this information out with a text editor before sending the file)

When the debugging mode is on, an additional menu item named "Debug" will appear at the right of the help menu. This menu contains useful entries like "Delete all events on calendar Server" and "Unregister client". Please be extra cautious when using these. You might loose all your data !

The other common problem reported to me is the error message "Can not start sync session" at application startup time.

How to avoid "Can not start sync session !" at startup ?

For most users, this message indicates a problem in the Sync Service registration database. Please execute the following steps :

  • Ensure the application is not running,
  • Turn debugging mode as per instructions above,
  • Select the "Debug" menu item and then choose "Unregister client",
  • Confirm the operation,
  • Restart the application.

If you are still experiencing the problem, please contact me.

  1. No comments yet.
(will not be published)