Siebel CRM Desktop for Microsoft Outlook Administration Guide > How Siebel CRM Desktop Synchronizes Data > How Siebel CRM Desktop Handles a Conflict During Synchronization >

How Siebel CRM Desktop Handles a Synchronization Error

If a top-level error occurs, then the Synchronization Engine stops any further processing and displays a message to the user that describes the error. The engine also logs the message to a log file.

Table 5 describes where the Synchronization Engine stores the error message log file.

The following types of errors can occur in this situation:

• System error
• Resource allocation error
• General storage problem
• Application state malfunction
• Logic 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 perform 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 of an object changed since Siebel CRM Desktop queried the object during the current synchronization session, then Siebel CRM Desktop cannot perform the update and delete operations until the next synchronization cycle. In this situation, it creates an issue that it handles in the subsequent synchronization. This synchronization creates a collision because the object was changed since the last synchronization. A collision is a situation that occurs when the same record is modified on the Siebel Server and in Microsoft Outlook between synchronization sessions.