Log files in ELOxc EWS are stored in various locations on the computer. This section contains a list of the log files, what information they contain and where they are located.

Information: You can set the logging level in ELOxc Tools. You can choose a number between 0 (lowest logging level) and 20 (the highest number of log messages). You can also change this setting in the ELOxc.xml configuration file directly.

It is not recommended to lower the logging level unless it is absolutely necessary.

General logs:

General logs are usually stored in the ELOxc program directory. They cannot be configured to be stored in another location.

ELOxc_Base.log: This log file stores general information logged by ELOxc.exe that is not assigned to a specific instance. Values are written to the log when instances are first registered, as well as if an instance has not been successfully registered or other errors occur. It is normally stored in the ELOxc program directory. If the ELOxc service has been run at an insufficient level of privilege, it is stored on the drive root (C:\).

ELOxcSrv.InstallLog: This log file is created in the same directory as ELOxcSrv.exe. It stores information about the installation success or failure of the ELOxcSrv service.

ELOxcSrv_yyyy-mm-dd.txt: This log is created every day that the ELOxcSrv service runs (or attempts to run). It contains information about the status (start, stop, errors, etc.) of the ELOxc service and the various instances.

response_[timestamp]_[command].xml: These log files are stored in the Response folder of the ELOxc program directory. This folder is created along with the first ELOxc instance. They contain information about the success or failure of an ELOxc command (Start, Status, Mailboxes, etc.).

status_[instance name].xml: This log file contains a compact list of information about the active instance and the action trees within it. It is also stored in the Response folder.

Instance logs:

Instance logs are stored in the log directory defined when the ELOxc service is registered. Every instance has its own log directory. Every time the service starts, a child directory is created in this directory with a timestamp. This final directory contains the instance log files.

ELOxc_[timestamp]_ADQU.log: This log file contains the results of an LDAP query run by the instance, such as the detected Exchange accounts and stores. It can be useful to check whether the query is configured correctly and whether it completes successfully. If the query does not detect the accounts you want to process, the instance will not run correctly, regardless of whether the action trees or other settings are correct.

ELOxc_[timestamp]_Main.log: This log file contains the results of a check of the entire instance definition and all action trees (including inactive action trees). The log also reports whether the Exchange server user is able to access and process the subordinate mailboxes. If an instance is unable to start because of an error, check this log first.

Exec_[timestamp].zip: This zip file contains logs of every processing run for an instance. If an ELOxc instance runs every minute, a new file is created every minute. The logs are compressed to save disk space, but you may optionally choose to leave the logs uncompressed in the log folder.

ELOxc_[timestamp]_Exec.log: This file is stored in the zip file above. It logs the process of querying the mailboxes for an instance.

ELOxc_[timestamp]_Worker_[number].log: This file is stored in the zip file above. A separate log file is created for each worker thread within an instance, with counting starting at 00. It logs the progress of the action trees run through in the instance. If an error is encountered during a processing run, this log file displays the node in the tree in which it occurs. You can then use the GotoId script to locate and correct the affected node.

ELOxc_Update logs are also stored within the instance log directory.