How Siebel CRM Desktop Handles Synchronization Errors

If a high-level error occurs during synchronization, then the Synchronization Engine stops any further processing and displays a message to the user that describes the error. The following types of errors can occur:

• System error

• Resource allocation error

• General storage problem

• Application state malfunction

• Login failure

• Connectivity problem

• Missing xml or js files in the customization package

If an operation failure occurs in the Synchronization Engine, then Siebel CRM Desktop creates a synchronization issue and then attempts to do this operation again during the next synchronization session. The following types of errors can occur in this situation:

• Unexpected failure during an add, update, or delete operation.

• If the data for an object changed since Siebel CRM Desktop queried this object during the current synchronization session, then it cannot do the update and the delete operations until the next synchronization cycle. In this situation, it creates an issue and then handles this issue in the subsequent synchronization. This synchronization creates a collision because the object changed since the last synchronization. A collision is a data integrity problem that occurs if Siebel CRM Desktop modifies the same record on the Siebel Server and in Outlook between synchronization sessions. For more information, see Resolving Synchronization Conflicts.

Siebel CRM Desktop logs synchronization errors in synchronization log files and in the General Log log file. It does not enable log files, by default. For more information, see Log Files You Can Use with Siebel CRM Desktop.