Diagnostic Log Files

adTempus produces diagnostic log files that can be used for troubleshooting problems. Some error messages may request that you include these log files when you contact technical support.

Log Locations

Separate log files are created for the adTempus service, the adTempus Console, and the Job Host process. The log files can be viewed using a text editor such as Notepad.

adTempus Service

Log files for the adTempus service are found in the "logs" folder under the instance directory:

C:\Program Files\Arcana Development\adTempus\Instances\InstanceName\logs

For the default instance, InstanceName is "Default". If you installed adTempus to a different location, the folder will be under that location.

The current log file is named "adTempus.service.log". Previous log files are named "adTempus.service.log.1" through "adTempus.service.log.9". Each time the adTempus service is restarted, or if the log file reaches 10MB in size, a new log file is started.

adTempus Console

Logs for the adTempus Console are found in the "adTempus jobhost" folder under the TEMP folder ("%TEMP%") for the user running the Console. The current log file is named "adTempus.console.log". Previous log files are named "adTempus.console.log.1" through "adTempus.console.log.9". Each time the Console is restarted, or if the log file reaches 10MB in size, a new log file is started. adTempus

Job Host

The Job Host process hosts execution of scripts and some other operations. Log files for the Job Host are found in the "adTempus jobhost" folder under the TEMP folder of the user whose account the job is running under. The log file is named "adTempus.jobhost.nnnn.log", where nnnn is the Windows Process ID (PID) of the Job Host process. Old log files are deleted automatically.

Log Contents

During normal operation, adTempus writes to the log files only when it detects potential problems. Generally such issues are also reported to the user, through error messages or Alerts in the Console. The diagnostic log files contain additional details that can be used to trace the cause of the problem.

Enabling Debug Logging

When diagnosing a problem it is sometimes necessary to have adTempus write more extensive information to the logs. Follow these steps when instructed to do so by support personnel:

  1. Run the "adtloggingconfig.exe" program.
    • To configure logging for the Console, run the program from the Console program folder.
    • To configure logging for the service or Job Host, run the program from the "bin" folder for the appropriate instance (e.g., C:\Program Files\Arcana Development\adTempus\Instances\Default\bin).
  2. Check the Enable debug logging option for the service, Console, and/or Job Host, as appropriate.
  3. Click OK to save the changes and close the tool.

Changes take effect immediately and do not require a restart of the service or Console. adTempus will begin writing a second set of log files, with "debug" in the name (for example, "adTempus.service.debug.log", "adTempus.console.debug.log", and "adTempus.jobhost.nnnn.debug.log").

To turn off debug logging when it is no longer needed, run the tool again and uncheck the Enable debug logging option.

Sending Log Files

Include the log files when submitting a support request. Put all the files in a single compressed archive (ZIP or 7zip). Make sure the current log file is included: some ZIP utilities skip files that are in use. If this happens, copy the file and add the copy to the ZIP.

Keywords

ADT005054