SSSE: The First Transition Can Be Only Of TransitionType.

(Doc ID 2173582.1)

Last updated on MARCH 01, 2018

Applies to:

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


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.

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!



(httptransport.cpp (1047)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
(soapbinding.cpp (682)) SBL-EAI-04304: Unknown Part '' for operation 'CreateItem' exists in SOAP message.
(outdisp.cpp (267)) SBL-EAI-04308: Operation 'CreateItem' of Web Service '' at port 'ExchangeServicePortType' failed with the following explanation: "The first transition can be only of TransitionType.".

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

The issue has the following business impact:
Due to this issue, users cannot have LAST_SYNC_TS updated correctly.


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