Sun ONE Synchronization 1.1 Patch 2 Release Notes

Sun ONE Synchronization 1.1 Patch 2 is a software product that runs on a Windows personal computer and allows users to synchronize Sun ONE Calendar Server events and tasks with mobile devices and personal information managers (PIMs) such as Microsoft Outlook. The Release Notes are intended primarily for Calendar Server and system administrators. End users should refer to the Sun ONE Synchronization 1.1 Patch 2 online help for information. Sun ONE Synchronization was formerly iPlanet Synchronization 1.0.

The Release Notes document information available at the time of the release, including:

Read this document before your end users install and start using Sun ONE Synchronization 1.1 Patch 2. For an online version, see the following documentation Web site:

Revision History

Table 1 Revision History
Date	Description
November 21, 2003	Udated Supported PIMs and Mobile Devices for Palm Desktop and Palm OS support.
October 29, 2003	Initial Release Notes for Patch 2.

Supported Calendar Server Releases

Sun ONE Synchronization 1.1 Patch 2 is supported with the Sun ONE Calendar Server 6.0 and 5.1.1 releases.


Caution	Do not use Sun ONE Synchronization to migrate calendar data. For example, do not export Netscape Calendar Server 4.x data to a Palm device and then sync the data to Sun ONE Calendar Server. This type of migration can cause corruption in the Calendar Server database. To migrate Netscape Calendar Server 4.x data to Calendar Server, use the ncs4migrate migration utility. To obtain the latest version of ncs4migrate (and other Calendar Server migration utilities), contact your Sun technical support representative or account manager.

Supported PIMs and Mobile Devices

Sun ONE Synchronization 1.1 Patch 2 supports the following PIMs and mobile devices:

Requirements

Installation Notes

You can obtain the Sun ONE Synchronization 1.1 Patch 2 installation program from the Sun ONE download site or the Sun Java Enterprise System Accessory CD. Or contact your Sun technical support representative or account manager to obtain the program.

Pre-Installation Considerations

Before you install or upgrade (reinstall) Sun ONE Synchronization 1.1 Patch 2, consider these items:

Installing or Upgrading Sun ONE Synchronization 1.1 Patch 2

Upgrading (or reinstalling) Sun ONE Synchronization allows you to upgrade your current version of the Sun ONE Synchronization software or to add support for an additional PIM or mobile device.

To install or upgrade (reinstall) Sun ONE Synchronization 1.1 Patch 2, follow these steps:

Note: Depending on the platform your are installing on, you might need to restart your operating system. The installation program will prompt you if a restart is needed.

What’s New in Sun ONE Synchronization 1.1 Patch 2

No new features or enhancements are added in this release. This release fixes the problems described in the next section, Problems Fixed in This Release.

Problems Fixed in This Release

Table 2 Problems Fixed in Sun ONE Synchronization 1.1 Patch 2
Bug ID	Description
4754413	Syncing an all day event from Calendar Server will create the event a day earlier.
4760207	Recurring tasks with start and due date in the future are not synced properly.
4700267	Sun ONE Sync experiences problems when syncing huge events.
4911679	Wrong warning message is displayed when recurring events sensitivity (privacy) is changed.
4911844	Tasks with no due date are synced with dates to Calendar Server.

Known Problems and Limitations

Problems after Running the csvdmig Migration Utility

If your site runs the csvdmig migration utility to use hosted (virtual) domains, Sun ONE Synchronization users will see the following message when they try to synchronize their data to Calendar Server:

Cannot access calendar data source. Check general troubleshooting under online help.

The csvdmig utility adds a domain name to each calendar ID (calid) for calendar names in the Calendar Server database and LDAP directory server. For example, suppose you run csvdmig to migrate a user named jsmith, with the domain as sesta.com. A calendar name that was jsmith:public-calendar is changed to jsmith@sesta.com:public-calendar.

Consequently, Sun ONE Synchronization cannot find jsmith’s calendar with the revised name.

To synchronize with their Sun ONE Calendars, users must perform these steps (which are also included in the Sun ONE Synchronization online help):

Users should then be able to synchronize with their Sun ONE Calendars. If this doesn't resolve the problem, contact your Sun technical support representative.

Sun ONE Synchronization 1.1 Patch 2 Known Problems

Table 3 Sun ONE Synchronization 1.1 Patch 2 Known Problems
Bug ID	Problem Description
4943722	For Palm Desktop, Sun ONE Sync returns “A specified module is not found” error. When attempting to sync Palm Desktop data to Calendar Server 6.0, Sun ONE Sync returns “A specified module could not be found.” The rsSync.log file also indicates that the rstPalmDT.dll could not be found. This problem occurs when you configure the Palm Desktop to save your user data in a different folder than the default installation folder. For example, you install the Palm Desktop software in the C:\Palm folder, but you configure the Palm Desktop software to point to the C:\tmp folder for data storage. Workaround: Change the data folder in the Palm Desktop to the original default installation folder.
4771502	The list of events and their details are not displayed before confirming the delete of events.
4771491	Only one user at a time can use Sun ONE Synchronization.
4761025	Tasks are not synced properly between Calendar Server and a Palm device.
4758779	Sync shows conflict even if user modifies only one data source PIM or device. Sync an event from Calendar Server to a PIM or device, and then delete or add characters in the title, location, or notes, on the PIM or device. A subsequent resync back to Calendar Server results in a conflict. This problem was reported on Outlook, but it also occurs on other PIMs and devices.
4753692	Sun ONE Sync removes the fanned out record from Calendar Server without any warning. For example, create a recurring event on Outlook and sync to the Calendar Server. On the Calendar Server change a fanned out event to “Allday.” Sync again. On Outlook open the “Allday” series and modify the title. Sync again. On the Calendar Server the updated record is removed for the day without any warning.
4753688	Only exceptions made to the recurring events on Windows CE are synced to the Calendar Server.
4753684	Data gets duplicated when using filters and selecting “No” in the delete confirmation dialog. Recommendation: It is highly recommended that you do not select “No” when asked for a delete confirmation on syncing after applying filters, because this can result in duplicates in later incremental syncs.
4746149	While syncing, task fields with value of “None” are passed a value after syncing. For example, create a task on Outlook with the Start Date set to “None” and the Due Date set to a specific value. Sync to Calendar Server and edit the title for the task. If you sync again, on Outlook the Start Date is set to the Due Date value.
4742989	Changing mapping reports error and forces a full sync. Be very careful if you change the default mapping, and make sure you understand the functionality and semantics of the fields involved. Specifically, avoid mapping fields between different data types, and be careful not to change the mapped fields by editing them randomly. For example, suppose location on Calendar Server is mapped to notes on Palm, with the formula Note= “Event Located in:” + location. After syncing an event originating in Calendar Server with location information as Bangalore, the notes in Palm would read as ‘Event Located in: Bangalore’. Do not try to edit the placeholder, which in this case is ‘Event Located in:’. This can lead to unexpected behavior. If you want to change the location by editing in Palm, change only “Bangalore” to the new location.
4742979	Multi-day event is removed on Windows CE when modified on Calendar Server and synced. Sun ONE Synchronization 1.1 Patch 2 removes a multi-day event on Windows CE when the event is modified on Calendar Server and then synced back to Windows CE.
4741324	Once the final installation screen is displayed you cannot navigate back to the earlier screens to edit the selections made. However, the install instructions states that it is possible to navigate to the previous screens and edit the selection.
4740576	Tasks are not synced properly to Windows CE devices. Reminders on tasks are not synced when syncing between a Windows CE device and Calendar Server, because there is no default mapping for the reminder information. Do not turn on this mapping because it can cause tasks with reminders not to be synced and unpredictable behavior.
4740281	Record Filter shows only records created on the data source other than Calendar Server. When syncing with Palm Desktop, the Record option in the Filters show only the records that are created on the Palm Desktop and does not list the records that are created on Calendar Server.
4740280	When filters are set Sun ONE Synchronization deletes only those events that fall within the filter range. All events are not deleted. The document mentions that the filters can be applied only when syncing data between Palm Desktop to Calendar Server.
4738816	All day recurring events are not synced properly between Outlook and Calendar Server. All day recurring events originating from either Outlook or Calendar Server get synced to the other side as “fanned out” all day events for the first sync. However, later modifications on the fanned out events on the other side (not the source), results in improper and unpredictable behavior. It may also cause errors and force a full sync.
4738794	Data duplication occurs with Sun ONE Synchronization. Data duplication can occur in these instances: Using the Combine option for a full synchronization can cause extensive data duplication. Recommendation: Avoid using the Combine option. Unusual usage patterns can result in duplication in case of recurring events. Recommendation: Edit recurring events only on the source (originating) calendar.
4738734	Sync reports an unknown error and forces a full sync because of a translator exception. This problem was reported for the Outlook translator, but an unknown error also occurs for translator exceptions for other PIMs and mobile devices.
4738714	Deleting notes for an event on Palm or Windows CE devices is not reflected in Calendar Server. Create a new event on a Palm or Windows CE device with some text in the notes field and then sync to Calendar Server. If you delete the notes text on the Palm or Windows CE device and then resync to Calendar Server, the Calendar Server event still has the previous notes.
4734531	Sun ONE Synchronization does not create logs according to the levels defined. The debug log level was set to 1 (for errors). When an unknown error occurred and sync was aborted, the log file did not have a related entry. To get meaningful logs, set the log level to 5.
4731403	Changing the mapping does not force a full synchronization. If you change the default mapping, you are prompted Yes or No for a full sync. If you click Yes, a partial sync is done, although changing the mapping should force a full sync.
4727479	Sun ONE Synchronization prompts for deletion of a record while actually modifying a record. Sun ONE Synchronization 1.1 Patch 2 prompts for the deletion of a record when changing a record from normal to recurring and syncing the changes. For example, create a non-recurring event on Calendar Server and sync it to a PIM or device. Then, change the event on Calendar Server to a recurring event and resync. Sync prompts for the deletion of the event. Click Yes. Sync will delete and then recreate the event.
4724229	Performance when syncing large data sets is slow. Use date filters to sync large data sets, because filters sync only a subset from the master database to the slave database. However, keep in mind which is your master database. Sun ONE Synchronization 1.1 Patch 2 considers PIMs such as Outlook and Palm Desktop to be master databases and handheld devices to be slave databases when syncing with Calendar Server. Calendar Server acts as a master or slave database depending on whether you are syncing it with a handheld device or a PIM, respectively.
4724227	Full sync that merges data from different sources can cause problems. Using the Combine option for a full synchronization can cause extensive data duplication. Recommendation: Avoid using the Combine option.
4718294	Sun ONE Synchronization 1.1 does not sync categories properly.
4718208	Sun ONE Synchronization allows the user to sync between any two data sources. You can create a new profile to sync between unsupported combinations of data sources (for example, Palm Desktop and Windows CE devices); however, the profile might not be supported by Sun ONE Synchronization 1.1 Patch 2. See Supported PIMs and Mobile Devices.
4713249	Remove mail related information from Sun ONE Synchronization 1.1. Sun ONE Synchronization 1.1 does not support synchronization of email. However, not all email related information has been removed from the product. For example, Outlook still expects the Outlook Mail to be set as the default mail client. Also, when you choose a new profile such as Windows CE or Outlook, you get options to sync mail.
4712627	Due dates are synced erroneously when no due time is specified for tasks. Due dates are synced as one day before when no due time is specified for tasks. For example, create a task on Calendar Server with a Due Date set and the Due Time not set. Sync it with any PIM or mobile device. On the PIM or mobile device, Due Date is one day earlier than the date on Calendar Server.
4712034	Tasks with no due date are no synced properly between Palm Desktop and Calendar Server. Tasks on Palm Desktop with due date as “No Due Date” are synced to Calendar Server with due date of December 31, 2031. Tasks on Calendar Server with no due date are synced to Palm Desktop with due date January 1,2032.
4710896	Events on Calendar Server that continue to the next day not synced properly to Palm devices. Syncing a Calendar Server event that has crossed a day boundary to a Palm device returns a warning message. Then, the duration of the event is set to the end on the same day, and the next day view does not show any information for the event.
4710715	Reminders are not synced properly to a Palm device from Calender Server.
4708864	Untitled tasks on Palm can be synced with Calendar Server but vice versa is not allowed. You can sync an untitled tasks on a Palm device to Calendar Server, but you cannot sync an untitled task on Calendar Server back to the Palm device.
4689303	Recurring events and tasks are synced as individual events and tasks on the destination. When synced, recurring events and tasks are “fanned out” on the destination calendar and appear as multiple (non-recurring) individual events and tasks. Sun ONE Synchronization 1.1 Patch 2 can handle changes to recurring events and can sync them accordingly so that the originating calendar will reflect a modification to the recurring event. Therefore, modify the recurring properties for events and tasks only on the originating calendar.
4683162	Synchronization with Outlook XP is not supported.
4771486	Administrator must grant access permissions to the end user. Sun ONE Sync software must be installed by an Administrator. The Administrator needs to assign rights to the end users of the Sun ONE Sync directories. When a user without proper permissions tries to use Sun ONE Sync, the following error messages are displayed: User unable to login to server. The Sync tool is already in use by another user. Workaround. Install Sun ONE Sync as an Administrator and grant users permissions to the following directories: C:\CommonFiles\XCPCSync C:\ProgramFiles\Sun ONE Synchronization
4798014	Sun ONE Sync does not allow multiple calendars to be synchronized simultaneously.
4798149	Alarm not synchronized properly. Create a recurring event on Palm with reminders set and synchronize it to Sun ONE Calendar Server. Modify the first instance of the recurring event on Sun ONE Calendar Server and sync again. The alarm for the first event on Palm is reset to zero.
4798155	Second event gets deleted when synchronizing events from Outlook to Sun ONE Calendar Server. Create a recurring event that recurs daily for 10 days on Outlook. Change the start time of the first event and then sync to Calendar Server. On Calendar Server delete the first event and sync again. The event is deleted and a new event is created on Outlook. If the data is once again synced to Calendar, the event for the first day is created on Calendar Server but the event for the next day is deleted.
4798157	The End date/by field cannot be set for daily recurring events, when events are synced from Windows CE to Calendar Server. For example, create a recurring event on Windows CE device with recurrence pattern set to “Daily” and “5 Occurrences”. Synchronize the event to the Calendar Server. On the Calendar Server instead of 5 occurrences, 52 instances of the event is created.
4798158	The End date/by field cannot be set for weekly recurring events, when events are synced from Windows CE to Calendar Server. For example, create a recurring event on Windows CE device with recurrence pattern set to “Weekly” and “5 Occurrences”. Synchronize the event to the Calendar Server. On the Calendar Server instead of 5 occurrences, 11 instances of the event is created.
4798159	Notes for events are not updated correctly when events are synced from the Calendar Server to Palm Desktop. Create an event on Calendar Server with space between two lines. For example, <Line 1> <Line 2> Syncing Calendar events to Palm Desktop causes the text to be displayed on a single line on Palm Desktop. For example, <Line 1>[]<Line 2>
4823413	Single tasks or recurring tasks with due dates on Palm are synced a day earlier. Create a task on Palm with due date “tomorrow” and sync it to Calendar Server. The tasks is created on Calendar Server with due date “Today”.
4827595	Cannot sync in Quiet Mode if the autosynchronize option is set.
4828212	Recurring Events created on Palm and synchronized to Calendar Server are deleted on Calendar Server but not on Palm. Create and synchronize recurring events on Palm device. On the Calendar Server edit an event and sync it to Palm.The event is removed from the recurrence pattern on Palm. Now, delete the complete series of recurring events on Palm. All events except for the one just modified is deleted. Once again synchronize the data. All the events on Calendar Server are deleted including the one appearing on Palm.
4828279	Sync shows conflict for Windows CE events when records are modified only on Windows CE device. Create a recurring event on Calendar Server and sync it to the Windows CE device. Edit the first event on the Calender Server and sync the events again. Sync shows a conflict for that particular event.
4829611	Unknown Error is displayed when syncing recurring events occurring only on week days. Create a recurring event on Outlook. The event should recur daily for 5 week days. Synchronize the data to the Calendar Server. Editing the second event on the Calendar Server and synchronizing again displays an “unknown error” message.
4837668	i18n: Multiple data does not work properly with Sun ONE Synchronization translator in Outlook.
4729067	New line in notes created on the Calendar Sever are not synced to Windows CE device. When an event with more than one line of notes is created on Calendar Server and synced to Windows CE device, the multiple lines of notes are all concatenated to a single line of entry.
4847532	Using Sun ONE Sync with other XTND Connect Sync software may not work properly. Sun ONE Sync is not designed to work with other versions of XTND Connect Sync. Users must choose either Sun ONE Sync or XTND Connect Sync to synchronize data. They cannot use both versions to synchronize data.

Documentation

The following documentation was revised for Sun ONE Synchronization 1.1 Patch 2:

Localization

Sun ONE Synchronization 1.1 Patch 2 is available in English only and has not been localized in other languages. Release 1.1 has undergone limited internationalization (i18n) testing with favorable results for single-byte character sets including French, Spanish, and German. The results of i18n testing with Simplified Chinese, however, were unfavorable (see Bug IDs 4713884, 4713889, and 4713914). Localized versions for Simplified Chinese and other languages that use multibyte character sets may be available in a future release depending on the business requirements.

How to Report Problems

If you have problems, contact customer support using one of the following methods:

To help us assist you in resolving your problem, please have the following information available:

Sun™ ONE Synchronization 1.1 Patch 2 Release Notes

Version 1.1 Patch 2