Siebel Server Sync Guide > Administering Siebel Server Sync for Microsoft Exchange Server >

About SSSE Log Files


Log files for SSSE reside in the siebsrvr\log directory, along with log files for other Siebel software modules.

The amount of information that is logged can be tuned by adjusting log level settings. By default, multiple log files are created. For information about how to tune log levels or to consolidate log files, see Modifying SSSE Log File Settings.

The following information, which can be useful during troubleshooting, is logged for the Exchange Connector:

  • Exchange Connector successfully establishing a connection to the Microsoft Exchange Server
  • Exchange Connector processing domains for each user, including the number of records extracted for each domain for each user
  • Exchange Connector detecting a conflict

Other useful information that can be logged includes the following:

  • PIMSI Engine and PIMSI Dispatcher startup and shutdown information is captured in the log file whose name is of the form siebel.ComputerName.log, where ComputerName is the name of the computer where PIMSI Engine or PIMSI Dispatcher runs.
  • Several statements are typically logged regarding the beginning and ending of each extract session. This information is captured in log files that have names of the forms PIMSIEngxxxxx.log and PIMSIDispatcherxxxxx.log.

For examples of SSSE log messages, see Table 30.

Table 30. Typical SSSE Log Messages
SSSE Event
Example of Log Message for Event

User Extract Session Start

PIMSIEngSvc PIMSIInformational 3 0000000544a11a80:0 2006-06-27 04:56:10 (ssuserinit.cpp (3347)) BatchMgr: MADAMS: Starting extract for user.

Extract data from Exchange Start

PIMSIEngSvc PIMSIInformational 3 0000000544a11a80:0 2006-06-27 04:56:13 (exchangeconnector.cpp (830)) Connector: madams@esexch2.siebel.com: Extracting domain. PIM Domain Id = IPM.Contact.

Extract data from Exchange End

PIMSIEngSvc PIMSIInformational 3 0000000544a11a80:0 2006-06-27 04:56:16 (exchangeconnector.cpp (871)) Connector: madams@esexch2.siebel.com: Extracted 0 records. PIM Domain Id = IPM.Contact.

Extract data from Siebel Start

PIMSIEngSvc PIMSIInformational 3 0000000544a11a80:0 2006-06-27 04:56:16 (ssuserinit.cpp (4906)) BatchMgr: MADAMS: Starting extraction for Siebel Domain PIMSI Intermediate PersonalContact.

Extract data from Siebel End

PIMSIEngSvc PIMSIInformational 3 0000000544a11a80:0 2006-06-27 04:56:17 (ssuserinit.cpp (4958)) BatchMgr: MADAMS: Extracted 0 records for Siebel domain PIMSI Intermediate PersonalContact.

Import an Exchange record to Siebel

PIMSIEngSvc PIMSIDebug 5 0000003744a11a80:0 2006-06-27 06:47:29 (ssuserinit.cpp (1545)) BatchMgr: MADAMS: Pushed row: RowID=05349df89d16844da90998f8cdaedf54000000234ca3, User=madams@esexch2.siebel.com, Domain=IPM.Appointment.

Export a Siebel record to Exchange

PIMSIEngSvc PIMSIDebug 5 0000004344a11a80:0 2006-06-27 07:14:31 (ssuserinit.cpp (803)) BatchMgr: RBROWN: Pushed row: RowID=42-5HDSZ, User=RBROWN, Domain=PIMSI Intermediate Business Contact.

User Extract Session End

PIMSIEngSvc PIMSIInformational 3 0000004344a11a80:0 2006-06-27 07:15:34 (ssuserinit.cpp (3604)) BatchMgr: RBROWN: Successfully extracted domain All Domains for user RBROWN.

For information on the SSSE error messages that can occur when a user's data is synchronized, see Synchronization Error Messages.

Siebel Server Sync Guide Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.