Trace files from service applications (and printer drivers) are handled somewhat differently from those for desktop applications.  For desktop applications, FFTRACE needs to be run on the same machine and collects trace messages via Windows messages, into a common nodename.FTn file, where n is the day-of-week number.  This common trace file is written to the folder defined in FFTRACE itself.  For service applications, the application or DLL writes its own trace file, normally named appname_nodename.FTn.

For information about COPIAFACTS engine trace files (nodename.TRn), see below.

Trace File Location

The location for directly-written trace files is not determined by FFTRACE, which only sets location for the common trace file.

The location for directly-written trace files is chosen as the first of the following values to return a non-empty pathname:

Windows System Environment variable FFTRC

The folder C\FAXTEMP if it already exists

Windows System Environment variable GFAX

The trace folder defined by FFMRGNT for FFMERGE

The Windows 'temporary' folder

We strongly recommend that you use the FFTRC Windows system environment variable to define a folder for trace files on the local machine.

If the folder you select is not local, it must use a UNC path name, not  a mapped drive letter.

Trace File Name

The filename for directly-written trace files is normally the Application and Node name, for example COPIAFACTS_M3.FT1.  However the content of the file may include trace lines from multiple named sources, as for desktop applications.  For example COPIAFACTS_M3.FT1 may contain trace lines from CF8EMAIL.DLL and CF8SUPPORT.DLL.  Tracing from the DLLs is controlled, as for desktop applications, by using CF8EMAIL or CF8SUPPORT settings in the FFTRACE File/Applications menu.

Setting Trace Options

As for desktop applications, the level of tracing to be used for each application is set from the File/Applications menu in FFTRACE.

When making trace settings for CFMSG, FFTRACE must be run elevated (as administrator). Otherwise, for services run in a user account, FFTRACE should be run in the same account.
Setting the 'low-level' trace option for services may produce very large trace files.

Changes to trace level settings may take a few moments to be picked up by the running service.

Viewing Trace Files

Directly-written trace files may be viewed in TRCVIEW in the normal way.  Do not leave FFTRACE running to collect trace output from service applications and print drivers: it will only collect output from desktop applications on the same machine.

COPIAFACTS Engine Trace Files

Engine trace files named nodename.TRn are written in the same way as for a desktop application, when COPIAFACTS is running as a service.  They are written by default to the FAXFACTS folder, but this can be overridden by placing a local foldername (or a remote UNC foldername, but this is not recommended) in the FFTRC Windows System Environment variable.