Log files

1E Setup logs

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

1E Server logs

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

Subsystem	Component
1E Master	1E portal UI and applications (1E)	1E\Tachyon\	Tachyon.Portal.log
	Consumer API	1E\Tachyon\	Tachyon.ConsumerAPI.log
	Coordinator service	1E\Tachyon\	Tachyon.Coordinator.log Tachyon.Instrumentation.log
	Experience Analytics web application	1E\Tachyon\	Tachyon.Experience.log
1E Catalog	Catalog UI (CatalogWeb - Admin sync)	1E\Catalog\	Catalog.Integration.UI.log
	Catalog API
	Catalog Update Service	1E\Catalog\	Catalog.UpdateService.log
Content Distribution	Content Distribution web application	1E\ContentDistribution	ContentDistribution.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]
1E 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

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 the product is 1E, SLA Platform, and 1E 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 time zones.

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 log4net.

1E Server log files

For any issue, 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\*

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.

Platform	Logpath
1E Client logs on Windows	%ALLUSERSPROFILE%\1E\Client\1E.Client.log (used by 1E Client and 1E 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 client log	%ALLUSERSPROFILE%\1E\Client\Shopping.log
WakeUp client log	%ALLUSERSPROFILE%\1E\Agent\WakeUpAgt.log By default, Windows resolves %ALLUSERSPROFILE% as C:\ProgramData\

Configuration

1E Client log:

The LogPath setting is stored in the 1E.Client.Conf file and determines the full path and filename of the 1E Client log file.

The 1E Client log is shared by:

• 1E Client.

• 1E client features.

• Shopping client module (only available on Windows OS).

To change the logging level, please refer to LoggingLevel in the 1E.Client.CONF file.

The following are not configurable in this version:

• Maximum size of 5MB

• 5 rollover files numbered 1 (newest) to 5 (oldest) with the rollover number included as n.log

Nomad client log:

LogFileName registry is configurable using MODULE.NOMAD.LOGPATH and MODULE.NOMAD.LOGNAME installer properties.

• MaxLogFileSize is configurable using MODULE.NOMAD.MAXLOGSIZE. Default is 5242880 (5MB).

• When the log file reaches its maximum size, it is renamed with a .LO_ extension and a new .LOG file is created. The .LO_ file is overwritten each time.

PXE Everywhere Agent log:

LogFileName registry is configurable using MODULE.PXEEVERYWHERE.LOGPATH installer property, with the default filename PXEEverywhere.log.

• MaxLogfileSize is configurable using MODULE.PXEEVERYWHERE.MAXLOGFILESIZE. Default is 1048576 (1MB).

• When the log file reaches its maximum size, it is renamed with a .LO_ extension and a new .LOG file is created. The .LO_ file is overwritten each time.

• The logfile format is configurable using MODULE.PXEEVERYWHERE.LOGFORMAT default (1) is Configuration Manager-compatible format.

Shopping client log:

Not configurable using installer properties. Configurable by modifying the Log4Net settings in the Shopping.UI.exe.config file, located in %ProgramFiles%\1E\Client\Extensibility\Shopping folder.

WakeUp client log:

LogFileName registry is configurable using MODULE.WAKEUP.LOGPATH and MODULE.WAKEUP.LOGFILENAME installer properties.

• MaxLogFileSize is configurable using MODULE.WAKEUP.MAXLOGFILESIZE. Default is 1048576 (1MB).

• 5 rollover files numbered 1 (newest) to 5 (oldest) with the rollover number included as n.log

• In previous versions of WakeUp the .LOG file was renamed with a .LO_ extension and a new .LOG file is created. The .LO_ file is overwritten each time.

The table below lists the names and locations of log files created by the PXE Everywhere components.

PXE Everywhere component	Folder	Log file
1E Client	C:\ProgramData\1E\Client	1E.Client.log
PXE Everywhere Central	C:\ProgramData\1E\PXELite	WebService.log
PXE Everywhere Responder	C:\ProgramData\1E\PXEEverywhere	PXEEverywhereResponder.log
PXE Everywhere Agent	C:\ProgramData\1E\PXEEverywhere	PXEEverywhere.log

If the issue is related to PXELite boot media creation/updating using CreateBootImage.exe then please provide the following:

C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\CreateTsMedia.log

If the issue is related to the deployment of PXELite boot image into the TFTP folder of PXELite agent then please provide the following:

C:\ProgramData\1E\PXElite\CreateBCD.log

Names and locations of log files created by Content Distribution.

Content Distribution logs

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

For issues relating to	Required log files	Location of log files
1E Client	1E.Client.log NomadBranchUninstall-YYY-MM-DDThh_mm_ss_000Z.log	Default location: %ALLUSERSPROFILE%\1E\Client\
Content Distribution client	NomadBranch.log	Default location: %ALLUSERSPROFILE%\1E\NomadBranch\ Optional location if installed using 1E Client Deployment Assistant (CDA): C:\WINDOWS\CCM\Logs\
OS deployment	NomadPackageLocator.log NBCacheActions.log All Configuration Manager logs including SMSTS.log	The path changes at the different stages of an OS deployment.
ContentDistribution integration	ContentDistribution.log	%ALLUSERSPROFILE%\1E\ContentDistribution\
Delivery Optimization monitoring and reporting	NomadBranch.DO.log	Default location: %ALLUSERSPROFILE%\1E\NomadBranch\ NomadBranch.DO.log is created when Delivery Optimization monitoring and reporting are enabled using the DeliveryOptimizationReportingEnabled registry value.

• Mandatory uninstall logs: This is only logged when a mandatory uninstall is attempted on 1E Client devices. If uninstall fails, you can troubleshoot by using this log): C:\Windows\Temp\AppClarity.SofwareReclaimer.log

• 1E Client logs: Containing Reclaimer module logs: C:\ProgramData\1E\Client\1E.Client.log

• Optional/Mandatory API logs: This is on server side and will log all incoming APIs from the 1E Client Reclaim module and their response: C:\ProgramData\1E\SLA Platform\WebExternal.log

• ReclaimConsolidation: If the report fails or does not trigger after an Optional/Mandatory respond to the server with results, then refer to: C:\ProgramData\1E\SLA Platform\Web.log

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.

The method of configuring logging levels uses the above text values, where -log=0 is the default to mean the same as -log=info.