Sun Java System Communications Services 2005Q4 Release Notes

Known Issues and Limitations

This section contains tables that list of the more important known issues at the time of the Calendar Server 6 release:


The following limitation is known at this time:

Removing all Instances of Multi-Valued User Preferences

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.

Finding Installed Patches in a Clustered Environment

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

Pop-up Blockers

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.

Provisioning Users for Communications Express in Schema 1 Mode

Limitation: The csuser utility does not enable users it creates for Address Book.

Workaround: Enable the user using ldapmodify.

Multiple Domains (Hosted Domains)

Limitation: The configuration program,, 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:

  1. Enable hosted domains.

  2. 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.

Calendar Server Does Not Expire LDAP Cache Data

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.

Must Enter Both Fully Qualified and Non-fully Qualified Hostnames in Configuration File

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.ip = "skate" = "" 
caldb.dwp.server.test12.ip = "test12"

Non-RFC Compliant Data in X-Tokens Must be Quoted

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 ":".

Reported Problems

The following is a list of problems reported on the product:


Problem: The Calendar Server utility cscal does not validate users before adding them to the owners list as secondary owners.


Problem: The Calendar Server migration utility csmig does not update icsSubscribed with the owners calendars.


Problem: Lack of ability to automatically purge obsolete cached LDAP data.

Workaround: Manually remove old cached LDAP data.


Problem: enpd crashes when opening and closing connections rapidly and concurrently.


Problem: When a user modifies an event and chooses the option to modify today’s event and all future events, all previous events are deleted and will no longer display in the UI.


Problem: SSL initialization fails in SSLv2 mode. Unable to make use of SSLv2 client.


Problem: Configuration program “Get” does not get baseDN . It fetches the install root. You must specify the base DN by adding the part that comes after the root.


Problem: If you start a process (such as enpd) and then disable it in the ics.conf file, when stop-cal is issued, the system will not stop the disabled process.

Workaround: Re-enable the process in the ics.conf file and then issue the stop-cal command. After all processes are stopped, then disable any processes you do not want running before issuing start-cal.


Problem: Hot backup log files not purged according to configuration settings.

Workaround: To prevent disk full service interruptions, periodically copy the log files to another location and start a new log file.


Problem: In Schema 1 mode with hosted domains, if the DC tree is missing or improperly provisioned, calendar utilities can fail. You must create the DC tree nodes prior to creating or otherwise managing calendars.

6203605, 6245878, 6246230

Problem:Administrators can't delete a domain from LDAP. commadmin domain purge does not remove entries with deleted as their icsStatus. They must have removed as the status. The recommended Calendar Server utility, csclean, does not change the icsStatus to removed .

Workaround:Use ldapmodify to change icsStatus to removed before running commadmin domain purge.


Problem: If DWP is disabled while the DWP process is running, stop-cal will not stop it. stop-cal should stop all services rather than just those enabled.


Problem: Vague error message. In a hosted domain environment, if the basednpassed tocsdomain does not exist. The actual message received is: “FAIL: icsLdapServer: Null argument to function.” This type of error message is vague because the error message originates several levels down and could be caused by many different circumstances. Rather than just passing the error through, the higher level program should interpret the error message before bubbling it up to the next higher level.


Problem: Leading white space stripped from description field when stored in calendar server.


Problem: Linux: On RedHat Linux 3.0 email notification is received with subject missing.


Problem: SSL can not be enabled or disabled on individual hosted domains. (RFE)


Problem: The error messages given by csdomain are vague and need to be more explicit.


Problem: When is called with the -saveState option and the state file specified doesn't include a path the state file is not created. For example: /opt/sun/calendar/sbin/ -saveState cs.state

Workaround: Always specify the full path name, where the state file should be created.


Problem: Using csclean to delete users in non-hosted domain mode fails to remove users from LDAP.

Workaround: In non-hosted domain mode, use csuser delete to delete users from LDAP.


Problem: On Linux systems, if Calendar Server is shut down incorrectly, can't restart Calendar Server after reboot.

Workaround: Delete the lock files from /opt/sun/calendar/lib/lock/__db.001.


Problem: For event notifications, long To: fields are sent as one long line without wrapping. This violates RFC 821. If the line contains over 1000 characters (SMTP line length limit is 1000 characters), Messaging Server truncates the line.

Workaround: Use wrapsmtp keyword for the relevant channel in Messaging Server.


Problem: Calendar Server process cshttpd crashes if logging into Calendar Express when service.http.calendarhostname is set. The default is null ("").


Problem: Calendar Server won't work in an HA environment with Sun Cluster on Solaris 10 without patch 120500.

Fix: Apply patch 120500.


Problem:Problem with recurring events. Sending in dtstart and dtend parameters with non-date-field modifications (using storeevents) causes data corruption.


Problem:If you upgrade Delegated Administrator from the Java Enterprise System 2005Q1 version to the Java Enterprise System 2005Q4 version, the Delegated Administrator configuration program ( config-commda) freezes.

Fix: There is a new patch available for Delegated Administrator. Do not use the one in the general release version of Java Enterprise System 2005Q4.