Working with Exchange Integration logs
You can view Exchange Integration logs in <My Profile> | Administration | Email and Documents | Exchange Server Integration | Logging. You can view log files for each user (User logs) or for all user mailboxes and the whole configuration (Generic logs).
You can also view the logs from the Sage CRM installation in
%ProgramFiles(x86)%\Sage\CRM\<InstallName>\Logs\Exchange Integration.
Users with rights to view their own log files can view them in My CRM | Exchange Integration Logs.
Setting logging levels
You set the logging level for the logs in the table below in <My Profile> | Administration | Email and Documents | Exchange Server Integration | Connection Management. For more information, see Exchange Server connection fields.
|
Log File |
Description |
|---|---|
|
User folder |
Logs activity information and skipped items on individual mailboxes and errors that occur on a single mailbox. |
|
Generic folder |
Logs errors and activity not associated with a specific mailbox. The exchangeConfiguration log is most likely to contain errors the occur on a webapp level. |
|
Exchange Configuration Log |
Contains all activity on the configuration of the Exchange Integration for any given day including connecting to the Sync Engine, connecting to the EWS endpoint, and connecting to specific mailboxes. The file name for this log is [date]ExchangeConfigurationLog.log. |
|
Exchange Conflicts |
Contains all conflicts for the Exchange Integration for any given day, for all mailboxes involved in a synchronization that day. The file name for this log is [date]ExchangeConflictLog.log. Also available as a user log, User Conflicts [date][username]_ConflictLog.log. |
|
Skipped Items - CRM to Exchange |
Contains all skipped items when synchronizing from Sage CRM to Exchange for the Exchange Integration for any given day, for all mailboxes involved in a synchronization that day. The file name for this log is [date]SkippedItemsCRMToExchange.log. Also available as a user log, User Skipped Items - [date][username]_SkippedItemsCRMToExchange.log. |
|
Skipped Items - Exchange to CRM |
Contains all skipped items when synchronizing from Exchange to Sage CRM for the Exchange Integration for any given day, for all mailboxes involved in a synchronization that day. The file name for this log is [date]SkippedItemsExchangeToCRM.log. Also available as a user log, User Skipped Items - [date][username]_SkippedItemsExchangeToCRM.log. |
|
Sync Activity - CRM to Exchange |
Contains all sync activity and sync-related errors for any given day for all mailboxes involved when synchronizing from Sage CRM to Exchange. The file name for this log is [date]SyncActivityCRMToExchange.log. Also available as a user log [date][username]_SyncActivityCRMToExchange.log. |
|
Sync Activity - Exchange to CRM |
Contains all synchronization activity and synchronization-related errors for any given day for all mailboxes involved when synchronizing from Exchange to Sage CRM. The file name for this log is [date]SyncActivityExchangeToCRM.log. Also available as a user log [date][username]_SyncActivityExchangeToCRM.log. |
You set the logging level for the logs in the table below in the log4j.properties file in the exchangesyncengine webapp WEB-INF folder.
|
Log File |
Description |
|---|---|
|
Exchangesynchronisation - log4j.properties file |
High level activity log that displays the number of records to be processed. In general, it indicates if an error response is retrieved from EWS or CRMJ. |
|
Exchangesyncengine |
Logs activity (including GETs and POSTs), HTTP error codes if received, and stack traces. |
|
Exchangesyncdefault |
Logs all synchronization activity. This displays everything that occurs in sequence. |
|
Exchangesynch |
Logs errors that occur on individual synchronization items going to CRMJ or EWS. |
|
Exchangesyncenginestacktrace |
Logs stack traces caused by exceptions. This is a useful starting point. |
Logging tips
- Don’t enable DEBUG logging on any webapp until you've identified the general area where the problem is occurring.
- If you're unsure which area is causing the error, archive logs and generate a new set of standard logs.
- If you believe an error is returned by Exchange, or the error is caused by data sent to Exchange, enable the general, inbound, and outbound CXF logs.
- If you believe the error is occurring in the CRMJ webapp, examine the CRMJ log files.
