Oracle CRM On Demand Desktop Administration Guide > How Oracle CRM On Demand Desktop Synchronizes Data > How Oracle CRM On Demand Desktop Handles a Conflict During Synchronization >

How Oracle CRM On Demand 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. Other errors might occur because of a lost connection to the server, or Oracle CRM On Demand Desktop might not be able to synchronize data due to a language or access problem. In these situations, the synchronization might be able to resume, instead of stopping. You must check the user's connection, as well as the user's access and visibility settings. This check ensures that the user has the appropriate rights to perform all the operations required by the role. The engine also logs the message in a log file.

Oracle CRM On Demand Desktop generates the following log files, which describe synchronization errors:

• Generic Log. This log is enabled by default.
• SOAP dump.
• Sync dump.

You can enable the SOAP dump and Sync dump log files from the Options dialog Advanced tab, by clicking Configure Logging and Reporting.

Table 4 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
• Connection problem
• Missing XML or JavaScript files in the customization package

If an operation failure occurs in the synchronization engine, then Oracle CRM On Demand 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 Oracle CRM On Demand Desktop queried the object during the current synchronization session, then Oracle CRM On Demand 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 Oracle CRM On Demand server and in Microsoft Outlook between synchronization sessions.