The following limitation is known at this time:
Limitation: Each set_userprefs command removes only one instance of a multi-valued preference.
Workaround: To remove all instances of a multi-valued user preference, you must issue one set_userpref command per instance.
For example: Perform a get_userprefs to list all of the user preferences. If there are multiple values for a preference, such as icsSubscribed , then you must issue one set_userprefs command to delete the preference for each of the values listed.
Limitation: There is no cluster specific showrev command that will show what is installed on the individual nodes of the cluster. (This is a generic problem, not just Calendar Server specific. You would run into the same difficulty with any product installed on a global file system.)
This is a problem when you want to update Calendar Server. You need to apply the patch to every node where Calendar Server was already installed. In addition you can’t apply the patch to a node if Calendar Server hasn’t already been installed on it. If you don’t know which nodes have Calendar Server installed and which do not, at the least, it will be confusing and cost you time trying to discover where Calendar Server is installed.
Workaround: Run the following command to see all of the nodes where Calendar Server is installed: pkgparam -v SUNWics5 | grep ACTIVE_PATCH
Limitation: Certain Calendar Server windows will not display if you have a pop-up blocker enabled.
Workaround: Disable pop-up blockers for the Calendar URL to ensure all Calendar Server windows will display.
Exception: Neither the Norton Inet Security AD_BLOCKER nor the Mozilla built-in POP_BLOCKER will affect Calendar Server windows.
Limitation: The csuser utility does not enable users it creates for Address Book.
Workaround: Enable the user using ldapmodify.
Limitation: The configuration program, csconfigurator.sh, configures only a single domain.
Workaround: If you need a multiple domain calendar environment (called either Virtual Domains or Hosted Domains), you must do two things:
Enable hosted domains.
Add the domains yourself using Delegated Administrator, or the csdomain utility if you are still using Sun LDAP Schema 1.
See Chapter 11, Setting Up Hosted Domains, in Sun Java System Calendar Server 6 2005Q4 Administration Guide and Chapter 13, Administering Hosted Domains, in Sun Java System Calendar Server 6 2005Q4 Administration Guide in the Sun Java System Calendar Server6 2005Q4 Administration Guide.
Limitation: (Also bug number 4777792) Cache can fill up, causing errors. Calendar Server does not expire the LDAP cache data.
Workaround: Periodically remove contents of file. Then restart Calendar Server.
Limitation: The configuration file asks for the hostname twice. Once fully qualified and the second time not fully qualified. For example:
caldb.dwp.server.skate.red.sesta.com.ip = "skate.red.sesta.com" caldb.dwp.server.skate.ip = "skate" caldb.dwp.server.test12.red.sesta.com.ip = "test12.red.sesta.com" caldb.dwp.server.test12.ip = "test12"
Limitation: If there is non-RFC compliant data in an X-Token, it must be quoted. For example, a colon in an X-Token must appear as ":".