Why is a 6.x Based Calendar Being Created When a Migrated Calendar 7 User Accesses Thunderbird's Lightning Client? (Doc ID 1378313.1)

Last updated on DECEMBER 02, 2015

Applies to:

Oracle Communications Calendar Server - Version 6.3 (JCS 6) and later
Information in this document applies to any platform.

Goal


Components involved in testing:

     Convergence 1.0-14.01
     Convergence 2-2.01
     Calendar Server 6.3-24.01
     Calendar Server 7.2-4.19

A group of user calendars were migrated from Calendar Server (CS) 6 to CS7.   To prevent the CS6 from being accessed or used by the migrated users, local.autoprovision was set to no in the ics.conf and cal.autoprovision was set to false via the iwcadmin command.  The CS6 version calendars for these users were also deleted from the CS6 database.

The problem was seen when a migrated user started up Thunderbird 7 with Lightning 1.0b7 and their CS6 calendar was re-created.

Why is the calendar still being created, despite the configuration changes, and how can this be changed so that it functions correctly - ie.  to prevent the calendar from automatically being created in Thunderbird/Lightning for Calendar Server 7 migrated users?

Note:  In addition to seeing this issue with Thunderbird/Lightning, the same behavior is also seen when one of the migrated users logs into Convergence 1.   Convergence 1 will only work with Calendar Server 6.x, not Calendar 7.x, so users who have been migrated to CS7 should be informed not to use Convergence 1 if it is still in the deployment.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms