SyncTask Log

Each SyncTask, when executing, creates and maintains a log file specific to the store connections related to the sync task. Note that this means that several tasks that all reference the same source and target store objects will use the same log file, however each task will have a distinct “activity” in the log.

The trace log format provides a mechanism to record “activity IDs” so that multiple threads or channels of action can be recorded in one log file and tracking of actions between activities can be viewed. In the Super-ExMerge implementation, the activity IDs are created as timestamps in the following way: 00000000-2019–0620–135055003226

Broken down, the elements of this constructed activity ID are as follows:

• “00000000” = Padding characters. No meaning.
• “2019” = Year
• “06” = Month
• “20” = Day
• “13” = Hour
• “50” = Minute
• “55” = Seconds
• “00” = Padding characters. No meaning.
• “3226” = Fractional second.

The picture to the right shows an example of a sync task log that has multiple activities within it. Activities in with red text indicate one or more errors occurred.

The sync task log will record detailed actions that occur thru the progression of the task.

The sync task log files can become large over time if a sync task is repeated many times, either by schedule or by manual restarts. If a request to send this log file is made, compressing as a zip file is recommended. However, the maximum size of these log files is 20MB. If a log reaches this limit during processing, the existing log file will be renamed with a count at the end if the name (ex: joe@source.com-to-joe@target.com (1).svclog) and a new log file created with the original name in its place.
Additionally, when a sync task is started, if a pre-existing log file is already larger than 4MB, it will be renamed as above and a new log file generated.

If the log file is deleted or moved, the sync task will create a new log file. However, moving or deleting the log file while a sync task is actively being processed, will cause the task to fail. Task logs are only created at task startup.

Sync Task logs are, by default, located in the following file system folder: C:\Users\Public\Documents\Priasoft\SuperExMerge\Logging.
A separate child folder is created under this location for each source-to-target task type. The possible log types are:

The filename format of a sync task log is derived from the identifier of the source and target stores. For example: joe@source.com-to-joe@target.com.svclog.