SSSE: SyncState Getting Corrupt After Some Time
(Doc ID 2175496.1)
Last updated on FEBRUARY 11, 2022
Applies to:Siebel Server Sync - Microsoft Exchange Server - Version 184.108.40.206.14 [IP2014] and later
Information in this document applies to any platform.
For some of the SSSE users, synchronization suddenly stopped due to invalid syncstate data sent from Siebel to Exchange.
User has been correctly set up for SSSE synchronization. Synchronization works flawlessly for some days, weeks, or even months. LAST_SYNC_TS is regularly updated and all appointments are being synchronized.
After a random amount of successful synchronization cycles, Siebel stops updating appointments on Exchange side. LAST_SYNC_TS is not updated anymore.
In the PIMSI logs, following error appears:
PIMSIEngSvc PIMSIDebug 5 000d5204575c0afc:0 2016-08-09 13:38:27 (ssuserinit.cpp (4732)) BatchMgr: ZEM: Could not extract records from PIM for PIM Domain: IPM.Appointment, Server type Exchange 2000. Error: 0x89521e.
PIMSIEngSvc PIMSIError 1 000d5204575c0afc:0 2016-08-09 13:38:27 (ssuserinit.cpp (3854)) BatchMgr: ZEM: Failed to process PIM Domain: IPM.Appointment.
The issue being related to an invalid syncstate token sent from Siebel to EWS.
What is synchstate and how it gets corrupted?
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