Note
This article references
<WebApp>/
,<WebSvc>/
,<ScdlSrvc>/
and<Temp>/
as a placeholder for the install location of the Web Application, Web Service API and the Scheduler Service and Exago’s Temp Path configuration flag respectively.
To configure logging, refer to the Application and Performance Logging article.
To access the log file:
<WebApp>Temp
. If General > Scheduler Settings > Enable Remote Report Execution is set to True the report execution will instead be be recorded in the Scheduler Log.Note
Occasionally IIS may lock this file and prevent the log from being written. To correct this problem, see Application Logging.
Similar to the Web Application, the Scheduler Service maintains a log file. Considering the Scheduler can reside on a different machine than the main application, the log file is written where the Scheduler is installed.
Since Remote Execution is handled by Scheduler Services, if Remote Execution is enabled in the environment, all report execution will be logged into the Scheduler Service’s log.
To access the Scheduler Service log file:
<logging>
to on in the Scheduler Service’s configuration file.<ScdlSrvc>\eWebReportsScheduler.log
. Scroll to the bottom of the log for the most recent activity.Similar to the Web Application, the Web Service API maintains a log file. Considering the Web Service API can reside on a different machine than the Web Application, the log file is written where the Web Service is installed.
To access the Web Service API log file:
<writelog>
to True in the Web Service API’s configuration file.<Temp>\WebReportsApiLog.txt
. Scroll to the bottom of the file for the most recent activity.Some implementations of the .NET API may write to a log file as well. In v2018.1+, the log file for the built-in logging methods defaults to <Temp>\WebReportsApiLog.txt
.