My Oracle Support Banner

SSSE: The First Transition Can Be Only Of TransitionType. (Doc ID 2173582.1)

Last updated on NOVEMBER 18, 2020

Applies to:

Siebel Server Sync - Microsoft Exchange Server - Version 8.1.1.14.14 [IP2014] and later
Information in this document applies to any platform.

Symptoms

When specific time zones are used, appointments are not synchronized and an error related to “TransitionType” is written to the log files.
The error can be immediately corrected by changing the user’s time zone to a different one.
Example:

Working time zone: (GMT+02:00) Athens, Istanbul, Minsk
Non-working time zone: (GMT+02:00) Istanbul, Ankara

After changing the user’s time zone from (GMT+02:00) Istanbul, Ankara to (GMT+02:00) Athens, Istanbul, Minsk the LAST_SYNC_TS is updated!

 

The error observed is:



The issue can be reproduced at will with the following steps:
1.Create a appointment in Siebel for a user with timezone as (GMT+02:00) Istanbul, Ankara
2. Submit Dispatcher Job.
3. Synch gets failed.
4. Change the user’s time zone from (GMT+02:00) Istanbul, Ankara to (GMT+02:00) Athens, Istanbul, Minsk
5. LAST_SYNC_TS is updated


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.