Skip to main content

1E 9.x (on-premises)

Log files

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

1E Setup logs

1E 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:

  • AEInstall.log

  • BIInstall.log

  • CatalogInstall.log

  • SLAInstall.log

  • Tachyon.Setup.log

  • TachyonInstall.log

Tachyon Server logs

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

Subsystem

Component

Tachyon Master

Tachyon Portal UI and applications (Tachyon)

1E\Tachyon\

Tachyon.Portal.log

Consumer API

1E\Tachyon\

Tachyon.ConsumerAPI.log

Coordinator service

1E\Tachyon\

Tachyon.Coordinator.log
Tachyon.Instrumentation.log

Experience application

1E\Tachyon\

Tachyon.Experience.log

Catalog

Catalog UI (CatalogWeb - Admin sync)

1E\Catalog\

Catalog.Integration.UI.log

Catalog API

Catalog Update Service

1E\Catalog\

Catalog.UpdateService.log

SLA

SLA/Platform APIs (Admin, Core External)

1E\Tachyon\

Tachyon.AdminAPI.log

SLA Platform UI (Platform)

1E\SLA Platform\

Web.log

SLA Engine

1E\SLA Platform\

Engine.log

SLA Integrate Services (Connector Manager)

1E\SLA Platform\

1E.SLAPlatformIntegrateAgent.log

1E.SLAPlatformIntegrateManager.log

1E.SLAConnector.<type>_sync.log

SLA Inventory

n/a

n/a

SLA Operations Provider (not currently used)

1E\Platform Consumer\

n/a

SLA databases (Data, Integrate, Shared)

n/a

n/a

BI

MDX API

SQL database

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

Tachyon Response

Core

1E\Tachyon\

Tachyon.CoreAPI.log

Background Channel (Background)

1E\Tachyon\

Tachyon.BackgroundAPI.log

Switch(es) (also includes a single Switch Host service)

1E\Tachyon\

Tachyon.Switch.4000.SW1.log
Tachyon.Switch.Host.log

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

In this version of 1E 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 1E 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.

1E server components use the log4net RollingFileAppender class. Details can be found in http://logging.apache.org/log4net.

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\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 Log files page for more details.

Logging Levels

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

Value

Description

Error

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

Warn

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

Info

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

Debug

Outputs debugging information in addition to all the previous levels.

Trace

Outputs the maximum information available. Used only in exceptional circumstances as it will generate huge amounts of logging output.

Warning

Logging levels should only be changed from info only if requested by 1E Support and reset to info after investigation is complete.

Tip

The method of configuring logging levels uses the above text values, where -log=0 is 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)

%ALLUSERSPROFILE%\1E\Client\NomadBranchUninstall-YYYY_MM_HHTMM_HH_SS_000Z.log

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

/var/log/1E/Client/1E.Client.log

Nomad client log

%ALLUSERSPROFILE%\1E\NomadBranch\LogFiles\NomadBranch.log

PXE Everywhere Agent log

%ALLUSERSPROFILE%\1E\PXEEverywhere\PXEEverywhere.log

Shopping WSA client log

%ALLUSERSPROFILE%\1E\Client\WSA.log

WakeUp client log

%ALLUSERSPROFILE%\1E\Agent\WakeUpAgt.log

Note

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.

Task

Logpath

Notes

Optout

C:\Users\{USER}\AppData\Local\Temp\ AppClarity.SoftwareReclaimer.log

Optout 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

C:\windows\Temp\AppClarity.SoftwareReclaimer.log

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.

Reclaim

C:\windows\Temp\AppClarity.SoftwareReclaimer.MSI.log

For a mandatory reclaim, if a reclaim occurs using an MSI then an MSI log file is also created.

Configuration Manager Console Extensions log

%ALLUSERSPROFILE%\1E\Tachyon\Tachyon.CmConsole.log

%ALLUSERSPROFILE%\1E\Tachyon\Tachyon.RunInstructionUI.log

The Instruction Management Studio (TIMS) log

%ALLUSERSPROFILE%\1E\Tachyon\Tachyon.InstructionManagementStudio.log

1E product pack deployment tool log

Tachyon.ProductPackDeploymentTool.log

In the same location as the tool.

In this section: