Bookshelf v7.8: Synchronization Error Messages

When SSSE synchronizes a particular user's data, the synchronization can succeed completely, succeed partially, or fail completely. This topic lists some of the validation error messages that indicate partially successful synchronization. These error messages, shown in Table 35, generally indicate a problem with an individual record—other records for the same user might synchronize successfully.

When a validation (or other record-level) synchronization error occurs, whether or not the user's sync state for a session is saved depends on how the administrator has configured the Always Save Syncstate parameter. For additional information, see Skipping Records That Generate Synchronization Errors.

Your administrator can configure SSSE so that the administrator is notified by email when a synchronization error is generated. For further information on configuring email notification of synchronization errors, see Process of Configuring Email Notification of Synchronization Errors.

NOTE: Validation errors are not generated for outbound (Siebel application to Microsoft Outlook) synchronization attempts. If an error occurs in a record during an outbound synchronization attempt, it indicates a serious error has occurred, for example, the Microsoft Exchange Server is not responding. In these cases, the user's sync state is not saved.

Table 35 contains a listing of some of the error messages that indicate partially successful synchronization.

Table 35. Synchronization Error Messages
Logged Message	Error Code	Cause and Result of Error
Failed to process the unresolved attendees for Siebel Row: row_ID, Siebel Domain: domain_name.	None	SSSE cannot save the unresolvable attendees for the appointment in the row indicated. SSSE does not synchronize the record that had the error, but continues synchronizing the user's other records. SSSE also saves the attendee data in a special table, so that if the Siebel record changes and is synchronized with Microsoft Exchange, the Microsoft Exchange record retains the unresolved attendees.
One or more records with the same key already exists.	IDS_ERR_EAI_SA_MULTIPLE_MATCH IDS_ERR_EAI_SA_DUP_ CONFLICT SSASqlErrDupConflict2 SSASqlErrDupConflict	SSSE found a duplicate record in the Siebel database. SSSE does not synchronize the record that had the error, but continues synchronizing the user's other records.
One or more required fields of this record are empty.	IDS_ERR_EAI_SA_MISSING_REQ_FIELD IDS_WRN_EAI_SA_DML SSASqlErrReqField	One of the required fields for this record is empty and there was no default configured. SSSE does not synchronize the record that had the error, but continues synchronizing the user's other records.
This record cannot be deleted because it does not exist.	IDS_ERR_EAI_SA_BC_NO_ DATA SSASqlErrRecordDeleted	SSSE cannot delete a record because it is not in the Siebel database (it was probably deleted earlier).
Value entered for one or more fields of this record is not compatible with its declared Data Type.	SSASqlErrValidation	The value for one of the fields in this record is not of the correct data type for the field. SSSE does not synchronize the record that had the error, but continues synchronizing the user's other records.
Number of characters entered for one or more fields of this record exceeds the declared Data Length.	SSAOMErrDataTooLong SSASqlErrBindVarOverflow1	A text field for this record has more characters than the corresponding Siebel database field can handle. SSSE does not synchronize the record that had the error, but continues synchronizing the user's other records.
One or more fields of this record has characters that are not compatible with this DB Code Page.	SSASqlErrUnicodeToCodePage SSASqlErrUnicodeConversion	At least one of the fields in this record is not compatible with the code page database. This condition typically affects multiple users. SSSE does not synchronize the record that had the error, but continues attempting to synchronize the user's other records. You may be able to correct this condition by inspecting the indicated record and changing any special characters to standard characters.
Alarm flag is checked for past appointment.	SSAOMErrAlarmTriggerTime Passed	The appointment being synchronized is scheduled in the past and has an alarm flag checked in the PIM record. SSSE synchronizes the record but does not synchronize the outdated alarm flag. No user or administrator action is required.
One or more picklist fields of this record have a value that is not part of the bounded picklist of values.	SSAOMErrBoundedPick IDS_ERR_EAI_SA_PICK_ VALIDATE	A value that SSSE is trying to use for a picklist field is not available in the picklist for the field. SSSE does not synchronize the record that had the error, but continues synchronizing the user's other records.