The creation of a log file is one of the very first processes that occurs when ELOxc starts.

If log files are not written immediately, there are two possible reasons for this:

• The file ELOxc.xml is configured incorrectly
• The ELOxc account does not have write permissions on the log directory.

For performance reasons, the logs are separated and not stored in a log file.

Settings

You configure the log settings in the ELOxc.xml file.

LogDir: "LogDir" is where ELOxc stores the log directory tree. It also contains the Windows service log as well as the ELOxc Workspace user interface log.

LogAge: You can specify the retention period for logs here. The default value 0 ignores the log age. Other values, i.e. greater than 0, are interpreted as the maximum log age in days up to a maximum of 365. Once logs reach the configured maximum age, they are automatically deleted.

Please note: If you have enabled automatic deletion of old logs, use a different path for the log directory than the one used for the installation directory. The delete routine deletes all files in the configured log directory, regardless of whether they are actually logs or not.

LogDetail: The log files in ELOxc do not have settings like "debug" or "info". Instead, granular logging is applied, i.e. the log level ("LogDetail") accepts values from 0 to 20. The higher the value, the higher the granularity is. The value 0 means no logs are created.

LogReplies: The "LogReplies" directory is where the result of each function call in ELOxc is stored. With version 12 of ELOxc and the new UI, the functions of the user interface and the service no longer communicate over HTTP. You can therefore suppress the directory with the parameter default="false".

Individual log outputs

A directory with the same name is created for each instance. This is where the main log and the logs for catalog requests, job directories, and job ZIPs are stored.

The following log outputs are written:

Srv: This file contains everything the process does on its own, such as start, basic structure, basic functions, top-level information, "UnhandledExceptionCatcher".

Wks: This log is currently being worked on.

Catalog: This log contains all catalog requests (LDAP, PS, EWS ...). For example, you can check the potential mailbox scope here.

Main: This is where the values initially read from the configuration are stored, which is why the configuration may not be usable. If the configuration is valid, the instance starts and logs the job starts. This is also where the license count is stored.

JobControl: When a job is started, ELOxc connects to Microsoft Exchange and processes the job according to the configuration. The action trees are called separately according to their "OrderId" and the configured (and resolved) mailboxes. As the process distinguishes between mailbox folders, messages are searched or selected for each combination (tree, mailbox, folder) and then transferred to the workers. "JobControl" represents the abstraction level of "ItemsTreeDef".

Worker or JobWorker: This is where processing takes place for all selected Exchange messages. The jobs represent the abstraction level of the individual actions.

JobErrors: Unexpected behavior can occur in the configuration for each processed message. These events are recorded in the log file "JobErrors".

Error analysis

The following examples are intended to show which log files may be relevant depending on the scenario:

However, the problem with error analysis is that the user does not necessarily see the whole picture so that actual events may not coincide with the user's findings.

If you want to check ELOxc systematically through to message processing, you may need to check the complete log sequence. The log sequence is: "Srv", "Main", "Catalog", "JobControl", "Worker", "JobErrors".