Names and locations of log files created by Tachyon Server, 1E Client, and Tachyon tools.

Tachyon Setup logs

Tachyon Setup creates a Setup log file for itself and an Install log for each of the components (if used) in the same folder as itself:

  • BIInstall.log
  • CatalogInstall.log
  • ContentDistribution.log
  • SLAInstall.log
  • Tachyon.Setup.log
  • TachyonInstall.log

On this page:

Tachyon Server logs

The default location for all Tachyon logs is the folder %ALLUSERSPROFILE%\1E


Tachyon Master

Tachyon Portal UI and applications (Tachyon)1E\Tachyon\


Consumer API1E\Tachyon\


Coordinator service1E\Tachyon\



Experience web application1E\Tachyon\


CatalogCatalog UI (CatalogWeb - Admin sync)1E\Catalog\


Catalog API
Catalog Update Service1E\Catalog\


Content DistributionContent Distribution web application1E\ContentDistribution


SLASLA/Platform APIs (Admin, Core External)1E\Tachyon\


SLA Platform UI (Platform)1E\SLA Platform\


SLA Engine1E\SLA Platform\


SLA Integrate Services (Connector Manager)1E\SLA Platform\




SLA Inventoryn/a


SLA Operations Provider (not currently used)1E\Platform Consumer\


SLA databases (Data, Integrate, Shared)n/a



[SLA-BI].[BI].[Event Log]

Tachyon ResponseCore1E\Tachyon\


Background Channel (Background)1E\Tachyon\


Switch(es) (also includes a single Switch Host service)1E\Tachyon\



Please refer to Services and NTFS Security if changing the location of log files.

In this version of Tachyon Server, some installers do not support the LOGPATH property and the logs folder is not configurable during installation.

Each component has a configuration file in the Tachyon Server installation folder structure, which contains log configuration details. Defaults are:

  • Filepath %ALLUSERSPROFILE%\1E\<product>\ where product is Tachyon, SLA Platform, and Catalog
  • Filename as shown in the table above.
  • Maximum size 10MB (2MB for Switch logs).
  • 2 rollover files numbered 1 to 2 with the rollover number included as n.log (5 rollover files for Switch logs).
  • Date and timestamps are UTC to help troubleshooters synchronize logs on systems in different timezones.

Switch logs have the following names:

  • The first Switch installed will typically have a log filename Tachyon.Switch.4000.SW1.log (where 4000 is the port it is listening on and SW1 is the config name in the SwitchConfiguration table in the TachyonMaster database).
  • Other Switches on the same server will have different config names appended. 
  • The log filename will be unique on a server, but there may be the same named log on a different server.
  • A Switch will continue to use the same log, unless the SwitchConfiguration table is modified so that a different ID is used.
  • If you see a Tachyon.Switch.log without a config name appended, this is a special case where a Switch cannot find its correct configuration, and has fallen back to using the template * row which has ID=1. In which case you will need to troubleshoot how that happened.
  • Rollover logs have numbers appended, for example Tachyon.Switch_A.1.log, up to a default maximum of 5.

Tachyon server components use the log4net RollingFileAppender class. Details can be found in

Summary of server log file locations

For any issue, please provide a zip containing log files from the following locations:

  • %ALLUSERSPROFILE%\1E\Catalog\*.log
  • %ALLUSERSPROFILE%\1E\ContentDistribution\*.log
  • %ALLUSERSPROFILE%\1E\Platform Consumers\*.log
  • %ALLUSERSPROFILE%\1E\SLA Platform\*.log
  • %ALLUSERSPROFILE%\1E\Tachyon\*.log

If you are having licensing issues, please include:

  • %ALLUSERSPROFILE%\1E\Licensing\*

Please refer to the Tachyon Platform 8.0 - Log files page for more details.

Logging Levels

The table below describes the logging levels which are configurable for server components.


Only outputs errors. An error is a serious problem, typically requiring operator intervention of some sort to restore full functionality.


Outputs errors and warnings. A warning indicates a potential problem, where the system can nonetheless function without intervention.


Outputs general information in addition to the errors and warnings. This is the default.


Outputs debugging information in addition to all the previous levels.

TraceOutputs the maximum information available. Used only in exceptional circumstances as it will generate huge amounts of logging output.
Logging levels should only be changed from info only if requested by 1E Support and reset to info after investigation is complete.

The method of configuring logging levels for the Tachyon Switch changed in v3.3 to using the above text values, but retains -log=0 as the default to mean the same as -log=info.

1E Client logs

1E Client logs on Windows

%ALLUSERSPROFILE%\1E\Client\1E.Client.log (used by 1E Client and Tachyon features, and Shopping client)


1E Client logs on macOS

/Library/Logs/1E.Client.Daemon.log (shows any service start errors)

/Library/Logs/1E.Client.log (shows the current operation of the 1E Client)

1E Client logs on other non-Windows platforms


Nomad client log


PXE Everywhere Agent log


Shopping WSA client log


WakeUp client log


By default, Windows resolves %ALLUSERSPROFILE% as C:\ProgramData\

Software Reclaimer logs

Every time the Reclaimer runs it will create a local log file of the process it is doing. The location and name of the log file depends on what task the reclaimer is doing.

OptoutC:\Users\{USER}\AppData\Local\Temp\ AppClarity.SoftwareReclaimer.logOptout mode is normally run under user context so that the user can interact with the dialog. This means the log file will be in the users Temp folder within the user profile.

Mandatory mode is normally set to run under system context, in order to process reclaim uninstall commands. Therefore, the log file will be under the system temp directory.

ReclaimC:\windows\Temp\AppClarity.SoftwareReclaimer.MSI.logFor a mandatory reclaim, if a reclaim occurs using an MSI then an MSI log file is also created.

Configuration Manager Console Extensions log



Tachyon Instruction Management Studio (TIMS) log


Tachyon Product Pack Deployment Tool log


In the same location as the tool.