The Sun™ Open Network Environment (Sun ONE) Calendar Server 5.1.1 Release Notes document information available at the time of the release including:
Sun ONE Calendar Server was formerly iPlanet™ Calendar Server.
Read this document before you install Calendar Server 5.1.1. For an online version, see the following documentation web site:
http://docs.sun.com/db/prod/s1calsrv
After you install and start using Calendar Server 5.1.1, check this web site periodically to view the most up-to-date documentation.
In addition to performance enhancements and bug fixes, Calendar Server 5.1.1 includes the following new features:
Calendar Server 5.1.1 has the following installation changes:
Calendar Express 5.1.1 has many new UI enhancements that can help your end users to be more productive. These new features are described in the following document:
Sun hopes you will make this document available to your end users so that they can take advantage of these new features.
The LDAP Calendar Lookup Database (CLD) plug-in provides horizontal scalability of the calendar database by allowing user and resource calendars to be distributed over a number of back-end servers for a single Calendar Server instance. The LDAP CLD plug-in uses the icsDWPHost attribute to determine the back-end server where a calendar is located.
To support the LDAP CLD plug-in, Calendar Server 5.1.1 includes:
The CLD cache option can improve the performance of the Calendar Server with the LDAP CLD plug-in by caching the DWP host server information (icsDWPHost LDAP attribute) for calendar users and thus reducing calls to the LDAP directory server.
To use the CLD database cache, make sure the following configuration parameter is set to "yes" (the default):
Other configuration parameters used by the CLD cache option are:
For more information about these new parameters, see the Calendar Server Programmer's Manual.
If you have customized your UI, consider the following changes:
componentlist Tag Replaces listeventcanvas Tag
In the 5.1.1 release, the componentlist tag replaces the listeventcanvas tag.
New Attributes Added to weekcal, componentlist, monthcal Tags
The format="optimize" attribute is added to the weekcal tag. When this attribute is used, the populated XML produced for the XSL is optimized, and the old XSL cannot be used to format it.
Code Example 1 shows the optimized format of the populated XML for weekcal tag. A declaration exists for each weekday in the week. (Saturday and Sunday can now be excluded.) These weekday declarations also include any all-day events and no-time tasks associated with the given day.
One timeblock declaration exists for each valid time block in the week. The earliest time block will be either defined by the user's start of day or by the earliest event/task in any day of the week (whichever comes first). The last valid time block is defined by the user's end of day or the latest event/task in any day of the week, whichever is later.
The numIntervals indicates how many table cells this event group will need. If the number of cells is greater than 1, the event group spans multiple time blocks. If the number is 0, the table cell was used in a previous row. Within a weekday, events are still listed as componentGroups.
The showbusylist="" attribute is added to the monthcal, componentlist, and weekcal tags. When showbusylist="" is included, the populated XML also contains free/busy block information for those calendars being viewed that provide availability access but not read access. The free/busy information is interspersed with the usual component information in the following format. For example:
<Busy e_Calid="jsmith" e_Calid_encoded="jsmith">
<StartTime iso="20020328T120000" year="2002" month="03" date="28"
hour="12" minute="00" seconds="00" dow="5" weeknum="13"/>
<EndTime iso="20020328T130000" year="2002" month="03" date="28"
hour="13" minute="00" seconds="00" dow="5" weeknum="13"/>
</Busy>
Populated XML for userctx Contains a New Attribute
The XML of the userctx tag has not changed, but the populated XML now also contains a user attribute indicating the user's language character set. For example:
<user name="john" firstName="John" lastName="Smith" fullName="John Smith"
mail="john.smith@sesta.com" language="ja"/>
The XSL changes in this release are extensive. To retain all of your own XSL, you can pick up all the new XML files, but you will need to remove the following new attributes:
Your XSL will not know how to handle the XML generated by these attributes.
The XSL changes modify the look and operation of the user interface in response to usability feedback on the Calendar Server 5.1 release. In particular, the New Event, New Task, New Group, User Search, and Repeating Event or Task dialogs are very different. Also, the Week view and Month view have been optimized to improve performance.
Most of the XSL files have changed; however, the files that have changed extensively are new_event.xsl, new_task.xsl, new_group.xsl, search_for_calendars_common.xsl, search_for_cals.xsl, weekview.xsl, monthview.xsl, and i18n.xsl.
The visible text strings in the XSL files have been converted to variables to simplify the localization process and are in the respective i18n.xsl file for each language (Bug ID 4537676). The XSL files are installed in the following directories:
server-root/cal/bin/data/language
where language identifies the specific language code.
You can localize the i18n.xsl file as required at your site. The i18n.xsl file contains the text strings referenced in non-localized XSL files as well as the text strings used in date_format.xsl (which is localized). You need to localize date_format.xsl only for languages whose format or layout differs from English.
The cstool utility now allows you to ping the Event Notification Service (ENS) service (enpd process) running on a local or remote server. The following command pings the ENS server as determined by the local.hostname parameter in the ics.conf file:
You can also use these options to ping an ENS service running on a remote server:
For a description if the cstool requirements and other options, see the Calendar Server Administrator's Guide.
ENS message notifications include these enhancements:
For problems related to these features, see:
New WCAP Parameter and X-Tokens for ENS Notifications
The new optional run-time application ID (appid) parameter allows certain WCAP commands to have the source of the command specified in an X-Token in a subsequent ENS message. The appid parameter is a user-supplied character string that accepted by these WCAP commands:
Note: The appid parameter is a run-time value and is not stored in the database. Therefore, the WCAP output or any exported events will not have the X-Tokens defined.
New X-Tokens for ENS Notifications are X-NSCP-COMPONENT_SOURCE and X-NSCP-TRIGGERED-BY:
If appid is not included in the WCAP command, or if the origin of the request is Calendar Express or a Calendar Server administration utility, X-NSCP-COMPONENT_SOURCE will have one of these values:
For more information, see the Sun ONE Calendar Server Programmer's Manual.
New ics.conf Parameters for ENS Notifications
To differentiate between a reply, refresh, or modify for an event in ENS notifications, Calendar Server includes the new configuration parameters described in the following table. To use this enhancement, the caldb.berkeleydb.ensmsg.advancedtopics parameter must be "yes".
For more information, see the Sun ONE Messaging and Collaboration Event Notification Service Manual.
ics.conf Parameters Reserved for Future Use in ENS Notifications
The ics.conf file also includes the following new configuration parameters. These parameters, however, are reserved for future use and are not used in the current release.
The Calendar Express Inform About Event option is now configurable with the following parameter in the ics.conf file:
ui.eventdialog.inform.enable = "no"
By default, this parameter is set to "no". To have Calendar Express display the "Inform About Event" option when Calendar Express users create or edit an event, set this parameter to "yes".
To set the locations of lock, process ID (PID), and counter files, use the following new ics.conf parameters:
To improve performance on Solaris systems, you can configure a memory-based file system (tmpfs) for the session database by setting the new ics.conf parameter local.instance.use.tmpfs to "true". The tmpfs file system is then overlaid based on the values of the service.http.sessiondir.path and service.admin.sessiondir.path parameters.
For more information, see the tmpfs(7FS) and mount_tmpfs(1M) man pages for the Solaris documentation.
The local.ugldapicsextendeduserprefs parameter in the ics.conf file has these new settings:
Starting with the Calendar Server 5.1.1 20020924 hotfix, the storeevents and storetodos WCAP commands use the default Calendar Server time zone in invitation and reminder email messages for new events and todos (tasks).
In releases before this hotfix, if the tzid parameter is omitted, the storeevents and storetodos commands use GMT for the start and end times in invitation and reminder email messages. For more information, refer to Bug ID 4730931.
The problems fixed in the Calendar Server 5.1.1 release are grouped as follows:
Table 2 lists the installation problems fixed in the Calendar Server 5.1.1 release.
Table 3 lists the client and Calendar Express user interface UI problems fixed in the Calendar Server 5.1.1 release.
Table 4 lists all other problems fixed in the Calendar Server 5.1.1 release, including administration, authentication, calendar lookup database (CLD), core, CSAPI, database, DWP, and WCAP problems.
Table 5 lists the internationalization (i18n) and localization (l10n) problems fixed in the Calendar Server 5.1.1 release.
This section contains information you should know before you install Calendar Server 5.1.1, including:
For installation information and instructions, refer to the Calendar Server Installation Guide.
To install, reinstall, or upgrade the Calendar Server, you must have superuser privileges. On Solaris or other UNIX systems, you must login as (or become) root (user ID = 0). On Windows NT systems, you must login as an administrator who has full administration privileges for the system.
Sun ONE Calendar Server 5.1.1 supports the following software platforms:
To run Calendar Server 5.1.1 on the Solaris 9 (5.9) Operating Environment, the 20021030 (or later) hotfix is required. To obtain this hotfix, contact your Sun technical support representative or account manager.
Table 6 shows the required patches for Solaris 8 (5.8). For the most current list of patches, check the patches_sparc_SunOS_5.8.list file in the instsupp/ directory after you unbundle the Calendar Server. The revision number following the dash in each patch ID identifies the minimum patch revisions; later revisions are acceptable. You can download these patches from:
Patch ID
Description
Table 7 shows the required patches for Solaris 2.6 (5.6). For the most current list of patches, check the patches_sparc_SunOS_5.6.list file in the instsupp/ directory after you unbundle the Calendar Server. The revision number following the dash in each patch ID identifies the minimum patch revisions; later revisions are acceptable. You can download these patches from:
Patch ID
Description
SunOS 5.6: Fixes the Traditional Chinese TrueType fonts (zh-TW releases only)
Solaris 2.6 (5.6) supports Netscape Directory Server 4.12 and 4.16 but not iPlanet Directory Server 5.1.
Note
Calendar Server 5.1.1 supports Microsoft Windows NT 4.0 with Service Pack 6a (or newer). If necessary, you can download Service Pack 6a from the following web site:
http://www.microsoft.com/ntserver/nts/downloads/
Considerations for Installing on Windows NT Servers
To run Calendar Server 5.1.1 on Windows 2000 with Service Pack 3 (or later), the 20021030 (or later) hotfix is required. To obtain this hotfix, contact your Sun technical support representative or account manager.
Sun ONE Calendar Server 5.1.1 installation CDs are written in ISO 9660 format with Rockridge extensions (RRIP). To install Calendar Server 5.1.1 on an HP-UX system from an installation CD, you must first make sure that the Portable File System (PFS) is running and that you use pfs_mount (1m) to mount the CD.
For information about how to use PFS, see your HP-UX product documentation.
Before you install Calendar Server 5.1.1 on HP-UX 11.0 servers, install the 9/01 HP-UX 11.0 Quality Pack, which is available from the following web site:
Before you install Calendar Server 5.1.1, use the settings shown in the following table as a baseline for kernel tuning. (These settings are based on an HP 9000 with 2 GB physical memory and 2 GB swap.)
Parameter
Description
New Setting
To modify the kernel, use HP-UX system administration tools (sam and kmtune), or to modify the kernel manually:
On HP-UX 11.0 servers, the Calendar Server is not started automatically after a successful installation or restart, even if you select these options during installation. You must start the Calendar Server manually using the start-cal command. (4525117).
Sun ONE Calendar Server 5.1.1 supports these directory servers:
Note: iPlanet Directory Server 5.0 is not recommended for use with Calendar Server 5.1.1.For more information about directory server requirements, see the Calendar Server Installation Guide.
If you are using the Calendar Search feature, see also Using Calendar Searches of the LDAP Directory Server.
The hardware requirements to install Calendar Server 5.1.1 are:
Calendar Express requires a JavaScript-enabled browser. For optimal performance, Sun recommends the following browsers for Calendar Server 5.1.1:
Browser
Solaris
Windows
Macintosh
Sun ONE Calendar Server 5.1.1 has been tested with iPlanet Portal Server 3.0 Service Pack 4 and Mobile Access Pack (MAP) 3.0.
If you install Portal Server after installing Calendar Server, see Installing Portal Server after Calendar Server changes permissions on /var/opt (4535775).
If you plan to install or upgrade a localized version of Calendar Server 5.1.1, you must ensure you have the correct installation archive file. This file identifies localization versions by including the following language codes in the filename: en-English (always included), fr-French, de-German, es-Spanish, ja-Japanese, zh-Simplified Chinese, and zhtw-Traditional Chinese.
For example, ics-5_1_1-export-en-de-es-fr_sparc-sun-solaris2_6_tar.gz would have localized versions of Calendar Server 5.1.1 for English, German, Spanish, and French.
If you do not have the installation archive file you need, contact your Sun technical support representative or account manager.
If you are performing an upgrade of Calendar Server, the installation program removes any out-of-date localized resources. For example, suppose you have Calendar Server 5.1 installed with English, German, Spanish, French, and Japanese localized resources. If you upgrade using the ics-5_1_1-export-en-de-es-fr_sparc-sun-solaris2_6_tar.gz installation archive file, the installation program installs new localized resources for English, German, Spanish, and French, but removes the out-of-date Japanese localized resources.
Before you install Calendar Server 5.1.1, remove any *.so_pre-Hotfix_* files, especially any files that might be in the server-root/cal/bin/plugins directory. Otherwise, some of these files might be automatically loaded from this directory and cause inconsistent Calendar Server behavior.
If you are upgrading or reinstalling the Calendar Server, you can have the installation program save all Calendar Server configuration and customizable files that have these extensions:
The installation program generates a report that indicates which files have changed. After the installation has finished, you can use this report to merge your customizations from the saved files into the newly installed Calendar Server 5.1.1 files.
The following migration utilities are available to migrate calendar data to Sun ONE Calendar Server:
The ics2migrate utility migrates Calendar Server 2.x data and LDAP user preferences to Calendar Server 5.1.1. ics2migrate is installed in the server-root/cal/bin/ directory.
The ncs4migrate utility migrates Netscape Calendar Server 4.x calendar data to Calendar Server 5.1.1. If you plan to migrate Netscape Calendar Server 4.x calendar data, contact your Sun technical support representative or account manager to obtain the latest version.
The csmig utility migrates a calendar database that was created before the Calendar Server 5.1.1 release to a new database that supports the LDAP Calendar Lookup Database (CLD) plug-in.
The csmig utility released with Calendar Server 5.1.1 has the following problems:
Updated versions of csmig will be available after the Calendar Server 5.1.1 release. If you plan to use csmig, contact your Sun technical support representative or account manager to obtain the latest version.
For information about using all of the migration utilities, see the Calendar Server Installation Guide.
If you are using calendar searches of the LDAP directory, you should index the icsCalendarOwned attribute to improve performance. You should also ensure that the values for the Size Limit and the Look Through Limit parameters in your LDAP directory server configuration are large enough so that searches complete properly.
Calendar searches of the LDAP directory server are enabled by the following parameter in the ics.conf file:
service.calendarsearch.ldap = "yes" (which is the default)
Improving Performance by Indexing the icsCalendarOwned Attribute
To determine if the calendar search performance of the LDAP directory server can be improved, try the following LDAP command:
ldapsearch -b "base"
"(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))"
where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Express Subscribe->Calendar Search dialog.
Tests have shown that with 60,000 entries, the above search took about 50-55 seconds without indexing icsCalendarOwned. After indexing, the above search took only about 1-2 seconds.
Netscape Directory Server 4.1x
For Netscape Directory Server 4.1x, index the icsCalendarOwned attribute by following these steps:
For information about Netscape Directory Server 4.1x, refer to the Netscape Directory Server 4.1 Administration Guide.
For iPlanet Directory Server 5.1, index the icsCalendarOwned attribute using the following command on UNIX systems:
server5/bin/slapd db2index -D slapd-serverID
-t icsCalendarOwned: eq,pres,sub:2.16.840.1.113730.3.3.2.11.1
where slapd-serverID is the full path to the slapd-serverID directory.
For more information, refer to the iPlanet Directory Server 5.1 Configuration, Command, and File Reference.
Checking and Setting the Size Limit and the Look Through Limit Parameters
To determine if the Look Through Limit (lookthroughlimit) and Size Limit (sizelimit) parameters are set to appropriate values, try the following command:
ldapsearch -b "base"
"(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))"
where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Express Subscribe->Calendar Search dialog.
If the LDAP server returns an error, the sizelimit or the lookthroughlimit parameter might not be large enough. Follow these guidelines to set these parameters:
The Calendar Server supports limited virtual domain mode, which allows customers to host multiple calendar sites on the same Calendar Server installation. Full virtual domain support is scheduled for a future release; however, a subset of virtual domain functionality is available with Calendar Server 5.1.1 (initially with the Calendar Server 5.0 patch 2 release). If you would like to use limited virtual domain mode, contact your Sun technical support representative. For additional information, see the following article:
http://knowledgebase.iplanet.com/ikb/kb/articles/4950.html
A Calendar Server high availability (HA) configuration uses two Solaris systems running a single instance of the Calendar Server. If one system fails, the other system will take over running the Calendar Server. For additional information, see the following article:
http://knowledgebase.iplanet.com/ikb/kb/articles/8031.html
Although this article was written for Calendar Server 5.1, it also applies to the 5.1.1 release.
Note: The Calendar Server HA configuration has been tested on Sun Cluster 3.0 U1 and U2 and Solstice DiskSuite (SDS) with UNIX File System (UFS). It has not been tested on Veritas Volume Manager (VxVM) or Veritas File System (VxFS).
iPlanet Calendar Server 5.0 will reach its End of Support Life (EOSL) on November 21, 2002. Existing Calendar Server 5.0 customers will not be supported after that date and should upgrade to the 5.1.1 release. To obtain the Calendar Server 5.1.1 release, contact your Sun technical support representative or account manager.
The version 2.x JavaScript UI and the fmt-out=text/js option in WCAP commands, which were supported in the Calendar Server 5.0 release, will not be supported for 5.0 customers after November 21, 2002. These features are also not supported in Calendar Server 5.1, 5.1.1, and future releases.
Calendar Server customers who use a JavaScript UI or the fmt-out=text/js option in WCAP commands do so at their own risk and should consider converting to an XML-based UI.
Sun ONE Calendar Server 5.1.1 has the following known problems. If available, a workaround is provided for each problem.
If back-end server is restarted, front-end server must be restarted too (4812916, 4855183)
If Calendar Server is configured with one or more front-end servers that are connected to a back-end server and the back-end server goes down or is disconnected, each front-end server must be manually restarted to re-connect to the back-end server.
On Solaris 8 and Solaris 9 systems, set the tcp_time_wait_interval parameter to 60000 (60 seconds) by adding the following command to the /etc/init.d/inetinit file on each front-end server:
/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000
The tcp_time_wait_interval parameter specifies the number of milliseconds that a TCP connection remains unavailable in the TIME-WAIT state after it has been closed. The port remains unavailable for the specified amount of time, so that a new connection does not inadvertently get packets that were intended for the old connection.
Do not set tcp_time_wait_interval to a value less than 60000. To examine its current value, use this command:
/usr/sbin/ndd -get /dev/tcp tcp_time_wait_interval
cscal create utility no longer creates calendars for existing users in LDAP (4781251)
In Calendar Server 5.1.1, using the cscal create utility to create a calendar for an existing user in the LDAP server who has not logged into calendar (that is, does not already have a calendar) returns an error.
Note: The behavior of the cscal utility has changed since the 5.1 release. Before an administrator can create a calendar for a user using cscal, that user must first be calendar enabled (have the icsCalendarUser LDAP object class). Calendar Server 5.1.1 also requires that all calendars have an owner, which is specified by the icsCalendarOwned LDAP attribute.
In Calendar Server 5.1.1, use any of these workarounds to calendar enable a user:
After upgrade user cannot create new event with 800x600 screen resolution (4773771)
After an upgrade from Calendar Server from 5.1 to 5.1.1, on a Windows computer with 800x600 screen resolution, the OK, Cancel, and Help buttons on the new event window are positioned off of the window and cannot be clicked.
var gDefaultPopupWidth='width';
var gDefaultPopupHeight='height';
where width and height determine the size of the popup window. You will need to change the values from their current values (550 and 650, respectively) to ones that work best for your installation. You need to change only the javascript.xsl file for the language you are using; however, it is recommended that you also change the javascript.xsl file for the other languages in you installation.
cscal utility returns error when creating a valid calendar (4769090)
If you use cscal to create calendars with the same name but with different case letters (such as Meetings and meetings), Calendar Server creates each calendar but the second cscal statement returns an error. For example:
./cscal -o tchang create Meetings
Calendar Meetings has been created
./cscal -o tchang create meetings
Calendar meetings has been meetings
LDAP error 20: Type or value exists
This problem occurs because the icsCalendarOwned attribute is a case insensitive string, and tchang:Meetings is considered to be the same as tchang:meetings.
The LDAP server and Calendar Server databases are out of sync. A Calendar Server database search works, but you might not be able to search calendars with the same spelling using the LDAP calendar search. In this case, the LDAP calendar search returns only tchang:Meetings, but the Calendar Express UI doesn't return an error.
Avoid using calendars with the same name with different case letters for a specific owner.
csuser utility cannot create users with LDAP CLD plug-in enabled (4749067)
If the LDAP CLD plug-in is enabled, the csuser utility cannot create a new user. It returns "LDAP error 2: Protocol error", and the LDAP server log file (/slapd-hostname/logs/errors) shows "no values for type icsDWPHost".
This problem is fixed in the Calendar Server 5.1.1 20021030 hotfix. However, if you have not installed this hotfix, you can create new users as follows:
csattribute -a icsdwphost=hostname add jsmith
Then, use csattribute to list the user's LDAP attributes to make sure the attribute is correct:
replace=1 in storeevents.wcap command doesn't work with a recurring events (4738461)
The new replace parameter in the storeevents.wcap command currently works only for single events and not for recurring events. When modifying a recurring event, the replace parameter is ignored, and the new values for multi-valued fields are appended to the original data.
Recreate the event with the required parameters. For example, if you have a recurring event that has the "cat1;cat2" categories and if you want to replace them with "cat3;cat4", replace=1 causes the resulting categories to be "cat1;cat2;cat3;cat4". To replace the "cat1;cat2" categories, you must delete the event completely and then recreate it with "cat3;cat4".
cshttpd process listens on all IP addresses (4737358)
If you set the service.listenaddr parameter to a dedicated IP address, the cshttpd process still listens on all IP addresses.
Do not use the service.listenaddr parameter. Instead, add the following new parameter to the ics.conf file and set it to the dedicated host name or IP address:
service.http.listenaddr = "hostname or IP-address"
Also, if you want the DWP process (csdwpd) to listen on a dedicated IP address, add the following new parameter to the ics.conf file:
service.dwp.listenaddr = "hostname or IP-address"
After you set either parameter, you must stop and then restart the Calendar Server.
csmig migration utility is missing the description for usage examples (4734453)
If you run csmig without any options, csmig displays its syntax and examples. However, csmig does not have descriptions for the examples.
Refer to the Calendar Server 5.1.1 Installation Guide for information about running csmig.
csmig migration utility usage examples are incorrect (4734450)
If you run csmig without specifying any options, csmig displays its syntax and examples. However, the usage display has these problems:
Refer to the Calendar Server 5.1.1 Installation Guide for syntax and information about csmig.
HP-UX: csexport and csimport command abort with library error (4734419)
On HP-UX, the csexport and csimport command results in a library error.
Use the Calendar Express export and import options to export and import the calendar data.
import.wcap does not trigger ENS notification (4729674)
An import.wcap command that includes the appid parameter does not trigger an ENS notification message.
cscomponents delete does not trigger ENS notification (4725163)
A cscomponents delete command does not trigger an ENS notification message.
Warning message needed that login is required when time zone is changed (4719346)
If you change the time zone for a calendar, the changes do not take immediately take effect.
Log out of Calendar Express and then log back in for the time-zone changes to take effect.
cshttpd process dies on Windows NT server (4673164)
On a Windows NT server running four cshttpd processes, one cshttpd process died. However, Calendar Server has run successfully without problems on other Windows NT servers.
The impact and probability of this problem occurring is believed to be low, since the processes have been up and running under normal stress loads. Under excessive loads not typical for Windows NT servers, there have been cases of one cshttpd process crashing (which is not easily reproducible), and that occurred only on specific servers.
Calendar Server Windows NT testing has gone through severe QA criteria of functional tests, manual tests, and stress tests. The results have been positive, and the reliability seems to be much improved over previous releases. This problem is being reported for completeness in the rare event of a crash. Considering all data points we have, we do not expect this to occur under most circumstances.
Note: In a Windows NT deployment with multiple CPUs, the Calendar Server architecture ensures that if a cshttpd processes dies, the remaining cshttpd processes will continue to handle end user requests. Alternately, you can always use the start-cal command or the Services dialog box from the Control Panel to restart the Calendar Server. End users will then need to log in again.
Calendar Server doesn't create all instances if repeat until date is earlier than default (4625452)
Create a repeating event. On the Daily tab, click Every weekday and specify a repeat Until date earlier than the default Until date. The Calendar Server creates only one or two instances of the event.
Use the default Until date or a later date, and then delete the events you don't need.
Until date for a repeating event shows one day after original date (4622462)
Create a repeating event that repeats every weekday and set a specific Until date. Then, if you edit the event and click "Change repeat pattern", the new Until date is one day after the original Until date. For the repeating event, the Calendar Server is using Zulu time rather than the local time. Also, the default for the Until date is reset to Forever. If you click OK, the Until date for the event changes to Forever. This problem is a duplicate of 4537499.
After you make your choices for a repeating event, review the choices and make sure that the default for the Until date is not set to Forever. If you have doubts, click Cancel and not OK.
Email notifications cause problems with Netscape Communicator (4560460)
In Calendar Express, email notifications can cause problems with Communicator. Calendar Server notifications are optimized by default for the Outlook client. Notifications are sent out in multi-part MIME formats - text/plain, text/html, and text/calendar. These formats are defined in the server-root/cal/bin/config/en directory.
With these default formats, the event notifications are not correctly rendered in Communicator. Being rendered in this case means that Communicator is trying to handle the text/calendar format that is optimized for Outlook. In Communicator it exposes the "More Details", "Accept", and "Decline" buttons. It also will display a "Error: 3.0 Unknown: (::)".
Events created on a Macintosh using Netscape Navigator 4.x contain corrupted data (4556675)
If you create a new event or task on a Macintosh using Netscape Navigator 4.x and then add a name, location, and description, extra characters are added at the end of the description.
If you need to create new events or tasks with a name, location, and description on Macintosh systems, use Netscape Navigator 6.x or Internet Explorer 5.x.
Search doesn't return expected results if the search string contains an asterisk (4555547)
The search for a calendar doesn't always return the expected results if the search string contains an asterisk (*).
Try the search again without the asterisk, using a search string of at least three characters.
User cannot set reminders to invitations before accepting or declining them (4552548)
If an user tries to set a reminder to an invitation before accepting or declining it, the action is not saved. Also, if a user brings up the invitation without accepting or declining it and then clicks OK, an error is logged to the http.log.
Do not set a reminder before accepting or declining an invitation.
Calendar Express doesn't allow "last day of the month" for repeating events (4541444)
Calendar Express does not allow you to specify the "last date of the month" (regardless of the date) for a repeating monthly event.
To specify the "last date of the month" for a monthly event, schedule the event to repeat on the "31st day of the month." The Calendar Server then automatically adjusts the actual last day for months with fewer than 31 days.
Installation program does not display default time zone or allow it to be set (4541260)
The default time zone for Calendar Server is "America/New_York". The installation program does not display this default or provide a way to change it. Also, if the system default time zone (which is OS specific) is different from "America/New_York", the installation program does not attempt to find a Calendar Server time zone that matches it.
None during installation. However, for importing files after installation, you can set the following time-zone parameter in the ics.conf file:
! Timezone ID used when importing files.
calstore.default.timezoneID = "America/New_York"
Also, for more information, see the following article:
http://knowledgebase.iplanet.com/ikb/kb/articles/4996.html
Export from Internet Explorer 5.5 does not work correctly (4540544)
If you are using Internet Explorer 5.5, the Calendar Express Export function saves the calendar as an HTML file and not in .ics or .xml format.
csbackup utility fails if target directory exists and -f option is not specified (4539252)
The csbackup utility fails if the target backup directory already exists (even if it is empty) and you do not specify the -f option. For example, the following command fails if backupdir exists:
# ./csbackup database backupdir
If the target backup directory exists, include the -f option when you run the csbackup utility. For example:
# ./csbackup -f database backupdir
You can also specify a non-existent target backup directory and let csbackup create the directory for you.
Calendar Overview has inconsistent method for displaying tasks (4538960)
The Task/Event box, which appears just below the date banner for both the Overview and Day views, does not display tasks consistently.
Calendar Express displays tasks in the Task/Event box on the Overview and Day views as follows:
The Calendar Server does not display future tasks because a calendar might have hundreds (or even thousands) of future tasks, and displaying all of them would quickly overflow the Task/Event box. To view future tasks for a calendar, use the week or month view.
Calendar Server allows double booking of calendars (4538774)
The Calendar Server allows double booking of a user's calendars even if user.allow.doublebook is set to "no" in the ics.conf file.
To prevent double booking for a user's calendar, run the cscal utility with the -k no option for each individual calendar.
Not everyone has the calendar entry after a meeting has been scheduled (4538591)
To invite an attendee who does not have a default calendar to a meeting, you must specify the attendee's email address. The Calendar Server then sends an email message using "mailto:" to the attendee with the event details, but it does not create a default calendar for the attendee.
The Calendar Server creates a default calendar for a new calendar user in either of these situations:
For information about cscal, see the Calendar Server Administrator's Guide.
Recurrence IDs (RIDs) are not in ISO8601 format (4537733)
The Calendar Server does not convert RIDs to ISO8601 format.
Do the translation to the time_t format before passing back in the RID. That is, translate the creation date in ISO8601 to the Zulu version of ISO8601 and then to time_t.
Note Do not use the C mktime() functions, because they use the system's time-zone information, which might not map correctly to the Calendar Server or user's chosen time zone.
Users cannot login to Calendar Server after running the cstool refresh command (4537598)
After a cstool refresh command is executed to force a refresh of the Calendar Server configuration, users cannot login through Calendar Express.
Stop and restart the Calendar Server manually using the stop-cal and start-cal commands. The configuration will be refreshed, and users can then login through Calendar Express.
Spaces in group calendar names cause problems (4537454)
A leading or trailing space in a group calendar name causes the Calendar Server to create another group calendar without the space.
Do not use leading or trailing spaces in group calendar names.
Auto-provisioning feature cannot be disabled for first-time user login (4537234)
By default, the Calendar Server creates a default calendar when a new user first logs into the Calendar Server, and currently, there is no option to disable this feature.
None. However, a new configuration parameter to disable this feature is planned for a future release.
Installing Portal Server after Calendar Server changes permissions on /var/opt (4535775)
If you install Portal Server after installing Calendar Server, permissions for the /var/opt directory are changed to 0700 (drwx------). A subsequent attempt to restart the Calendar Server (or a reboot) causes the following error:
Starting csadmind
Fatal error 70: Cannot open calendar database
csadmind is not started
Calendar service(s) not started
After installing the Portal Server, change the permissions for the /var/opt directory to 0775.
logout.wcap call always returns a status of -1 (successful) even for a failure (4535769)
A logout.wcap call always returns -1 (successful) even if the logout has failed.
To check if a session is still valid, call the check_id.wcap command and then check the returned X-NSCP-WCAP-CHECK-ID property. If the value is zero (0), the session is invalid and the logout was successful. If the value is 1, the session is still valid and you must call logout.wcap to logout again.
International characters display incorrectly in Calendar Express (4527700)
International characters entered in Calendar Server command-line utilities such as csresource using encoding other than UTF-8 display incorrectly in Calendar Express.
For command-line parameters that contain international characters to display correctly in Calendar Express, enter the characters using UTF-8 encoding.
Reminder emails should be encoded per user's LDAP preferredLanguage attribute (4526762)
When a user receives a reminder email message for an event or task, the message is encoded according to the user's LDAP preferredLanguage attribute (for example, ISO-8859-2 for Central European users). This problem is fixed for most languages, including Western, Central European, and multibyte languages such as Japanese, Chinese, and Korean. However, it is not fixed for Arabic, Hebrew, Russian, and Turkish. These users still receive reminder email messages encoded as ISO-8859-1.
Internet Explorer user can't export in XML format after having exported in iCal format (4525128)
If you export a calendar in Internet Explorer 5.5 or later in iCal format, you cannot then export the calendar in XML format. Internet Explorer does not display the Save window to select a location for the exported file.
Click the Internet Explorer Refresh button and then export the calendar. Or, go to another Calendar Express window such as View or Calendars, return to the Options window, and then export the calendar.
HP-UX: Calendar Server is not started after a successful installation or restart (4525117)
On HP-UX 11.0, the Calendar Server is not started after a successful installation or restart, even if you select these options during installation.
Start the Calendar Server manually using the start-cal command.
The following documents have been revised for the Calender Server 5.1.1 release. Part numbers (if available) are in parentheses.
The Calendar Express Online Help is available with the Calendar Express software. All other Calendar Server documentation is available on the following Web site:
In a configuration with front-end and back-end servers, all servers must all be running the same Calendar Server release. For example, you cannot have a front-end server running Calendar Server 5.1.1 and a back-end server running 5.1. All servers in this configuration must be running Calendar Server 5.1.1.
Sun ONE Calendar Server 5.1.1 has been localized in French (fr), German (de), Spanish (es), Japanese (ja), Simplified Chinese (zh-CN), and Traditional Chinese (zh-TW). To obtain a copy of a localized release, contact your Sun technical support representative or account manager.
For a Calendar Express end user to access a localized version of the Calendar Server, the character set required to render the particular language must be available in the end user's browser configuration.
You might also need to set the preferredLanguage LDAP attribute for your end users. To determine the current setting of preferredLanguage, use the csattribute utility:
where userid is the user ID of the end user.
If preferredLanguage is not set to the language code for the release you are running, reset it using csattribute. For example, the following commands reset the language code to French (fr) for user bkamdar:
csattribute -a preferredLanguage delete bkamdar
csattribute -a preferredLanguage=fr add bkamdar
For installation considerations, see Installing a Localized Version.
Several considerations for specific localized releases include:
If you have problems with Sun ONE Calendar Server, contact customer support using one of the following methods:
http://www.sun.com/service/sunone/software/index.html
From this location, use the CaseTracker and CaseView tools to log problems.
To help us assist you in resolving your problem, please have the following information available when you contact customer support:
To assist in reporting problems, Sun provides the capture_environment.pl tool, a Perl script that captures the current Calendar Server environment, including the ics.conf file, log files, calendar database files, platform information, and core files (if available). These files can be useful to Calendar Server development to debug problems.
For more information, see the following web sites:
Date
Description of Changes
In What's New in Calendar Server 5.1.1, added Default Time Zone in storeevents and storetodos WCAP Commands.
In Calendar Server 5.1.1 Installation Notes, replaced "Calendar Server 2.x JavaScript UI Files" section with "EOSL for iPlanet Calendar Server 5.0 and the 2.x JavaScript User Interface (UI)".
In Calendar Server 5.1.1 Localization, added an update that Calendar Server 5.1.1 has been localized in French (fr), German (de), Spanish (es), Simplified Chinese (zh-CN), and Traditional Chinese (zh-TW) and will be localized soon in Japanese (ja).
In Known Problems and Limitations, added problems 4769090 and 4749067.
In Changes to the Documentation, added problem 4764577.
In Calendar Server 5.1.1 Localization, added considerations for localized releases including Traditional Chinese (zh_TW) and Japanese (ja).
In Supported Software Platforms, added support for the Solaris 9 Operating Environment and Windows 2000 operating system.
In Using Calendar Searches of the LDAP Directory Server, added information about indexing the icsCalendarOwned attribute to improve performance and setting the values for the LDAP server Size Limit and the Look Through Limit parameters.
In Known Problems and Limitations: Revised the workaround for Email notifications cause problems with Netscape Communicator (4560460) to refer to Article 5017 rather than 4964. Added problems 4773771 and 4781251.
In Calendar Server 5.1.1 Localization, added an update that Calendar Server 5.1.1 has been localized in Japanese (ja).
Added the Revision History.
Added description and workaround for If back-end server is restarted, front-end server must be restarted too (4812916, 4855183).
Copyright 2002 Sun Microsystems, Inc. All rights reserved.
Sun, Sun Microsystems, the Sun logo, Java, Sun ONE, iPlanet, and all Sun, Java, and Sun ONE based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
Netscape and Netscape Navigator are trademarks or registered trademarks of Netscape Communications Corporation in the United States and other countries.
Last Updated April 30, 2003