Working with TAC Server Logs

This article applies for TAC standalone and Array environment.

TAC logs are stored under “C:\Program Files\PortSys\TAC Gateway\Log\” Directory.

Following are the description of the log files and folders in TAC


Path

Description

AccessLogLogs all HTTP requests processed via TAC Gateway
ConfigUpdateApply Configuration logs are saved here.
DbLogTAC database logs are saved here
Execution\ContentLogSaves actual data of requests and responses sent via Http Server and Http Client modules of TAC. This is like HTTP packet tracing. This can be activated using TAC Gateway Tracing Tool.
Execution\EnvSaves logs of running configuration. This is the location that records operational activities of the TAC current configuration. Each apply configuration holds sets of following logs.
Execution\Env\<Config ID>\ActiveSyncSaves ActiveSync processing logs when device control is enabled
Execution\Env\<Config ID>\ConfigurationConfiguration log writes logs about configuration processing
Execution\Env\<Config ID>\DataLogWrites TAC SQL Database logging.
Execution\Env\<Config ID>\DataStoreWrites data store logs about user parameters such as device information and data store operation in AD LDS. Logs about data replication across multiple servers.
Execution\Env\<Config ID>\EnvironmentWrites general information about the TAC environment or configuration snapshot.
Execution\Env\<Config ID>\FileAccessWrites information about TAC File Access operation.
Execution\Env\<Config ID>\GenericWrites core information about TAC operation.
Execution\Env\<Config ID>\HTTPClientWrites information about communication between TAC gateway and backend servers using HTTP.
Execution\Env\<Config ID>\HTTPModWrites information about HTTP modification engine. Logs information about cookie filter, header changes, URL translation happening through TAC Gateway.
Execution\Env\<Config ID>\HTTPServerWrites information about HTTP request processing using TAC’s HTTP Server engine.
Execution\Env\<Config ID>\HTTPTunnelServerWrites information about SSL tunneling component and Client services component and client server communication such as RDP.
Execution\Env\<Config ID>\PolicyWrite logs about Access Policy evaluation and processing
Execution\Env\<Config ID>\PortalWrites events by portal web application such as application access.
Execution\Env\<Config ID>\ReportWrites logs when generate reports using reporting tool
Execution\Env\<Config ID>\SafeLoginWrite logs about SafeLogin process
Execution\Env\<Config ID>\SecurityWrites logs about Authentication and Authorization when accessing application
Execution\Env\<Config ID>\SessionWrites information about sessions in TAC.
GatewayMgrlog for Gateway Manager service. Which is used to synchronize array configuration and perform elevated operations, which are not available in TAC Gateway service, which is running under restricted Network Service account.


By default, TAC generate logs that are error, warning and informational in to the logs.

When you encounter any issues, you would be requested to send these logs by PortSys Support team for further analysis. In the event of log request you would need to send the logs for the current configuration environment in TAC.

Standalone TAC Server

Each configuration environment holds separate set of logs under its respective configuration ID under “\Env” folder. Configuration ID is generated by the Date and Time that configuration apply happened. Therefore it would be easier to find the current configuration logs by looking the latest configuration ID folder. You would be requested to zip and send the logs for further analysis.

The full folder path will be “C:\Program Files\PortSys\TAC Gateway\Log\Execution\Env\<Current Configuration ID>”

Below is the example of configuration ID:

TAC in Array

In array environment logs are saved as same as standalone server. Administrator would need to identify which array node handling sessions during an issue when traffic is load balanced.

To identify the node, administrator needs to open TAC Management Console on Array manager and go to Session Monitor under Tools menu.

Session monitor will display what sessions are running on what node. Locate the server name of the required user session and go to that array node to collect logs. 

In some cases, you would need to extract verbose logs about the TAC operation to identify the cause. TAC Gateway Tracing tool will allow you to collect verbose logs of the TAC environment. Read more about TAC Gateway Tracing Tool.