Sun™ ONE Synchronization 1.1 is a software product that runs on a Windows personal computer and allows users to synchronize Calendar Server events and tasks with personal information managers (PIMs) and mobile devices.
This document is intended primarily for system administrators. End users should refer to the Sun ONE Synchronization 1.1 Readme file, User's Guide, and online help for information.
Sun ONE Synchronization 1.1 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. For an online version, see the following documentation Web site:
http://docs.sun.com/db/prod/s1.s1cals#hic
Check this site periodically to view the most up-to-date documentation.
Sun ONE Synchronization 1.1 has been tested with and is supported only with Calendar Server 5.1.1.
It is recommended that you install the Calendar Server 5.1.1 20020924 (or later) hotfix to use with Sun ONE Synchronization 1.1. This hotfix fixes these sync related problems:
Sun ONE Synchronization 1.1 supports the following PIMs and mobile devices:
To install and run Sun ONE Synchronization 1.1, you need the following:
Version 1.21 or higher of the CDO library DLL must be installed and registered. If you need to install this DLL, run the install program for the Microsoft Office Suite or the Outlook application and install Collaboration Data Objects. If this DLL is already installed but not registered, make sure it is in the Windows system folder and then register it with this command: regsvr32 CDO.dll.
To obtain the Sun ONE Synchronization 1.1 installation program, contact your Sun technical support representative or account manager.
Pre-Installation Considerations
Before you install or upgrade (reinstall) Sun ONE Synchronization 1.1, consider these items:
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, 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.
Sun ONE Synchronization 1.1 has the following known problems.
Bug ID
Problem Description
Help topic for Auto Synchronize on the Settings window does not exist.
Syncing contact information from Outlook to Palm does not work.
Tasks are not synced properly between Calendar Server and a Palm device.
Recurring tasks with start and due date in the future are not synced properly.
When upgrading, deselecting an existing translator doesn't remove it from the Start menu.
Syncing all-day events from Calendar Server will create an event a day earlier.
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.
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.
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.
Multi-day event is removed on Windows CE when modified on Calendar Server and synced.
Sun ONE Synchronization 1.1 removes a multi-day event on Windows CE when the event is modified on Calendar Server and then synced back to Windows CE.
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.
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.
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.
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.
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.
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.
Sun ONE Synchronization prompts for deletion of a record while actually modifying a record.
Sun ONE Synchronization 1.1 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.
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 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.
Full sync that merges data from different sources can cause problems.
Using the Combine option for a full synchronization can cause extensive data duplication.
Sun ONE Synchronization 1.1 does not sync categories properly.
Sync does not show the attendees field in Outlook translator.
There is no support for the attendees field in the Outlook translator for events.
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. See Supported PIMs and Mobile Devices.
Sync cannot sync recurring events after than January 16, 2003.
If you sync a recurring event from a PIM or mobile device that has "No End Date" for the recurring pattern, events after a specific date are discarded. From testing on Outlook and Windows CE devices, up to 70 records are synced starting from the system date of the personal computer where Sun ONE Synchronization 1.1 is installed.
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.
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.
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.
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.
Reminders are not synced properly to a Palm device from Calender Server.
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.
Sun ONE Synchronization returns unexpected results while syncing large size events.
While syncing events with large descriptions, unexpected results occur. For example, syncing an event from Calendar Server with a description greater than approximately 1.04 MB returned unexpected results.
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 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.
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.
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.
Recurring events on Palm device results in deleted event on next resync to the Palm device
Recurring events on a Palm device are synced as individual events in Calendar Server and not as repeating events. If you then change one of the events in Calendar Server, a subsequent resync back to the Palm device deletes the entry on the Palm device.
In addition to the Release Notes, Sun ONE Synchronization 1.1 includes the following documentation:
The Help topic for Auto Synchronize is missing from the online help (Bug ID 4766491).
Note: This option is available only if you install a translator for Palm or Windows CE devices.
If the Automatically Synchronize upon connection is checked, synchronization starts automatically each time the mobile device is connected to the personal computer (which must be turned on).
If you enable auto synchronization, simply connect the mobile device to the personal computer and synchronization will begin automatically. You do not need to make any other menu selections for synchronization to occur.
Sun ONE Synchronization 1.1 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.
If you have problems, 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:
For more information, see the following web sites:
Copyright 2002 Sun Microsystems, Inc. All rights reserved.
Sun, Sun Microsystems, iPlanet, and the Sun logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
Netscape Navigator is a trademark or registered trademark of Netscape Communications Corporation in the United States and other countries.
Last Updated November 11, 2002