Event IDs and Transaction IDs
When MFT Platform Server writes an event to the Windows event log, it provides an Event ID. MFT Platform Server also writes transaction IDs for each of the transfers in the Windows event log.
The transaction IDs are broken down into two categories: local and remote. A transaction is assigned to one of these two categories by the MFT Platform Server initiator at the earliest possible time during the transfer. The transaction ID assigned is unique for all machines.
If a transaction is displayed in an event log before it is issued a transaction ID, the transaction does not have an ID number in the event log. For example, a transaction ID is not assigned if a failure occurs before a connection to the remote system is established. The transaction is not assigned an ID by the remote system because it never actually gets to the remote system.
In addition to the transfer ID, there are three additional types of information provided on the Event Properties dialog: message specific, error severity, and retry information.
Message specific information provides you with the details of the particular transfer ID that you are viewing at that time. The information includes the remote file name, local file name, transfer direction, and so on. Following the message information is information about the severity of the error. If the transfer fails with a severe error, this is indicated in the message. If the error is anything other than a severe error, MFT Platform Server retries the transfer if the Try Count is set to a value greater than one. If MFT Platform Server retries the transfer more than once, the retry information states the number of times that the transfer is attempted before it completes successfully or unsuccessfully.