Chat now with support
Chat with Support

Coexistence Manager for Notes 3.8.1 - User Guide

About the CMN Documentation Suite Introduction CMN Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Starting and stopping the Directory Connector service
CMN Mail Connector
Mail Connector features overview Coexistence mail routing basics Deployment of CMN Mail Connector Installation Configuration Mail Connector Management Console
CMN Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C: CMN Logs

Log files for the Mail Connector

Logs are stored in the Logs subdirectory under the Mail Connector folder.

Mail Connector log files are configured in the file
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Mail Connector\log42net.config

The configuration section for each log file is listed below.


section <appender name="LogFileAppender" ...>


section <appender name="ErrorLogFileAppende


section <logger name="SmtpFileAppender" ...>

Log files for the Free/Busy Connector

Logs are stored in the Logs subdirectory under the Free Busy Connector folder.

Free/Busy Connector logs are configured in the log42net.config file for each log listed below. The complete file path is
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Free Busy Connector\...


...\Free Busy Connector\EWS\bin\log42net.config


...\Free Busy Connector\Autodiscover\bin\log42net.config


...\Free Busy Connector\DominoFreeBusyService\log42net.config


..\Free Busy Connector\ExchangeFreeBusyService\log42net.config

Configuring CMN logging

A CMN configuration file will roll over to a new file (close the existing log file and create a new one) when its contents reach a particular size, or a particular time of day (e.g., midnight). Also, the log4net utility will create up to a certain number of sequential files before deleting the oldest to preserve disk space. By default the rollover method is size (default 10MB), to a default maximum of 25 sequential files, but these are configurable values, as noted in the procedure notes below.

Editing configuration settings in a CMN configuration file

To edit any of the configuration settings in a CMN configuration file:

For the Mail Connector’s SMTP.log file (only): If you want to enable or disable SMTP logging altogether, find the section
<logger name="CMN. SmtpProtocol.logging" ...>, and then:
For a Directory Connector or Mail Connector log (only): Find the corresponding section in the open file (section name also appears in the right-hand column above).
For any/all component log files: Make any desired changes. Values must be enclosed in double quotation marks and followed by a trailing space and slash character as shown in the field notes below.
<file value="[PathAndFilename]" />: Location and name of the log file that log4net will generate. The path specification can be absolute (e.g., "C:\log4net\CMN.log") or relative to the installation directory (e.g., ".\log4net\CMN.log").
<threshhold value="INFO" />: Scope and level of detail to appear in the logs. A valid value is any of these single words:    OFF FATAL ERROR WARN INFO DEBUG ALL
The values as listed here are in ascending order of detail, left to right, and the log will contain items at and above (to the left of) the specified value. For example, <threshhold value="WARN" /> tells log4net to include WARN, ERROR and FATAL events in the log file. The level is set to INFO by default.
<rollingStyle value="Size" />: Determines what will trigger log4net’s closing of a current log file and opening of a new one: either a change in calendar date, or a log file reaching a particular size. Parameter value is set to "Size" by default, or change to "Date" for the alternative.
<maximumFileSize value="10MB" />: Maximum log file size—the size at which log4net will close the current log file and open a new one (applies only if <rollingStyle value="Size" />.
<maxSizeRollBackups value="25" />: Maximum number of log files to keep—after which log4net deletes the oldest log file to create a new one.
Close and Save the configuration file under the same filename.
NOTE: Note: Any changes to the log42net.config file are immediately applied by the CMN service when the configuration file is saved.

For more detailed information about the log4net utility and how its log files can be configured, see the log4net Config Examples at the web site.

Related Documents