Siebel CRM Desktop for Microsoft Outlook Administration Guide > Administering Siebel CRM Desktop > Administering Features That Affect Performance >

Administering Tracing and Logging

The EAI Object Manager performs logging for the business service methods, uses component events to log information for the Siebel Adapter business service, and creates log files that capture the following information on the Siebel Server:

• Input messages
• Time
• Detailed error messages
• Trace

EAI stores these logs in the following file:

Siebel Server install directory\eaiobjmgr_lang.log

In UNIX, Siebel CRM Desktop stores these log files at the following location:

$SIEBEL_ROOT/enterprises/ENTERPRISE NAME/SERVER NAME log

For more information, see the topic that describes event logs in Siebel System Monitoring and Diagnostics Guide.

To administer tracing and logging

• Set the EnableLogging parameter to true.

  For more information, see the topic about common event types for Application Object Manager diagnostics in Siebel System Monitoring and Diagnostics Guide.

How Siebel CRM Desktop Handles Errors During Synchronization

If the current version of Siebel CRM Desktop is not compatible with the downloaded customization package, then Siebel CRM Desktop does not apply the package. Instead, it displays an error message to notify the user, and then records an entry in the CRMDesktopX.log file, where X is an incremental number that uniquely identifies the log file name. Siebel CRM stores the error message in the most recent log file. For information about where Siebel CRM Desktop stores this log file, see Where Siebel CRM Desktop Stores Data in the File System.

If an error occurs while the customization package is downloaded, then Siebel CRM Desktop displays an error message near the taskbar. The error notifies the user that the customization package changed but Siebel CRM Desktop cannot download it because of certain errors. The problem might be due to the fact that the user does not possess the required privilege on the Siebel Server. In this situation, the user must contact the system administrator to acquire the necessary privileges, and then restart the synchronization.