Summary
In certain situations, especially during cases with Laserfiche Support, it may be necessary to configure event trace logging for Laserfiche Server and Laserfiche Full-Text Search services in order to capture the processes causing the issue. This article lists the steps to configure, turn on, and turn off event tracing for these services.
More Information
Laserfiche event tracing does not distinguish between various types of processes going on inside the system. It simply captures everything in the log file. For this reason, before event tracing is enabled, you should make sure that no other activity is going on in the system. The best times to take tracing may be during the lunch hour or after work hours when relatively few people will be logged onto the server.
The steps for enabling event tracing are as follows:
Enabling Tracing Via the Laserfiche Event Trace Viewer 8
Note: If you are on version 8.1 Server or later, you can quickly enable and disable tracing from the Laserfiche 8 Event Trace Viewer. Enabling tracing from the Laserfiche 8 Event Trace Viewer only enables tracing for the Laserfiche Server. If you want to enable tracing for the search engine, see the section on enabling tracing through Windows Performance Monitor.
The trace file will be an .etl file located in the directory you specify.
Enabling Tracing Via the Performance Monitor
In versions earlier than 8.1, tracing can be enabled from the Performance Monitor.
The Laserfiche Server service and the Search Engine service must be running in order for their respective trace providers to appear in the list. You can also configure tracing for the OS, the HTTP server, and SQL Server from here.
Enabling Tracing Via the Performance Monitor in Windows Server 2008
The Laserfiche Server service and the Search Engine service must be running in order for their respective trace providers to appear in the list. You can also configure tracing for the OS, the HTTP server, and SQL Server from here.
After the trace is configured and ready, you can right click on it to start and stop logging. Typically, you will need to start logging, reproduce the error, then wait several seconds and stop logging.
Additional Information
Log files that are of size 5MB or greater are typically difficult to open and navigate by support engineers. For this reason, sometimes it may be necessary to enable rollover trace logs so that each trace log's size is limited to 2MB or less.
The steps to configure rollover trace logs are as follows:
Configuring Rollover Tracing
This type of tracing will be required in situations where the errors are intermittent and/or the process that generates them takes a long time (and thus the non-rollover log files would be too large to be of any use).
After starting the trace log, start the process that generates the error. When the error is received, stop the event tracing. Go to your application event viewer (Control Panel > Administrative Tools > Event Viewer) and check its time stamp. Navigate to the location where the event trace logs are stored. Browse through them to find the log file with the corresponding time stamp (which will be in the mmddhhmm format). This trace file, as well as the ones before and after, will need to be looked at by support engineers.