...

Make sure that the FIX message was re-transmitted correctly. If not, contact your counter-party counterparty regarding malformed messages from their side.

...

Parse Error : Incorrect size of a repeating group. Expected: 1. In fact: 2. Parsing stopped at column: 228 in tag N/A in message E with sequence number 979

...

To revert this parameter after updating to the versions stated above, this parameter should be set to false. Additionally, for FIX Engine, the field should be set to false.

...

The authentication service doesn't send a response in time

<timestamp>   WARN    [LogonHandler]  <thread>  Session <SenderCompId, TargetCompId> : process logon failed  - request is timed out

...

Solution or troubleshooting steps

 Check the incoming FIX session logs and if there are no messages User Response (BF) then the issue is on the Authentification Service side.

INFO

...

FIXEdge can't create a log directory in the specified path

<Timestamp><timestamp>    INFOWARN    [Engine]  Session <Session_Name><SenderCompId, TargetCompId>: There Changewas state:an olderror state=Establishedwhile newcreating state=NonGracefullyTerminated
<Timestamp>    INFO    [Engine]  Session <Session_Name> : active session was closed non-gracefully (The confirming Logout message was received from the counterparty.)

Description or root cause

...

path <path>. Using default log directory <logDir>. The error reason: <err.message>.

Description or root cause

This WARN record occurs if FIXEdge C++ can't create a log directory for the FIX session in the specified path.

Solution or troubleshooting steps

Check the value of the LogDirectory property specified for this session.

INFO

The active session was closed non-gracefully

<Timestamp>    INFO    [Engine]  Session <Session_Name> : Change state: old state=Established new state=NonGracefullyTerminated
<Timestamp>    INFO    [Engine]  Session <Session_Name> : active session was closed non-gracefully (The confirming Logout message was received from the counterparty.)

Description or root cause

This message appears when the session was terminated by Logout and IntradayLogoutTolerance mode is enabled. This mode means that during the next session start the same set of logs will be used and the next Logon will be sent with sequence number previous+1 (unless you use ForceSeqNumReset=ALWAYS. See matrix of possible IntradayLogoutTolerance+ForceSeqNumReset combinations).

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that session was disconnected correctly and sequence numbers were preserved.

Reject task finished

<Timestamp>    INFO    [Engine]  Session <Session_Name> : Reject task finished

Description or root cause

 In FIXEdge there is an option to reject messages that should be routed into the session, which exists, but currently isn't available. This message appears when all such messages were rejected.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that session was disconnected correctly and sequence numbers were preserved.

...

the task was finished.

The backup session has the same parameters as the primary session

<Timestamp>    INFO    [Engine]  Session <Session_Name> : Reject task finished

Description or root cause

...

 The backup session has the same parameters as the primary session

Description or root cause

This message appears when the backup session has the same parameters as the primary session.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that the task was finished.

...

backup session

...

's parameters are the same as for the primary session.

A FIX Session storage type isn't specified

<Timestamp>    INFO    [Engine]  <thread> Session <Session_Name> : The backup session has the same parameters as the primary sessionproperty 'Session.TESTSESSION.StorageType' is not found. PersistentMM storage type is used

Description or root cause

This message appears when the backup session has the same parameters as the primary sessionThe option for storage type is not set so the most efficient storage type (PersistentMM) is used.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that the backup session's parameters are the same as for the primary session.

...

Make sure that the storage type is specified correctly. Check if there are spaces between the property and its value.

New log message storage was created

<Timestamp>   INFO    [Engine]  <thread> Session <sender, property 'Session.TESTSESSION.StorageType' is not found. PersistentMM storage type is usedtarget> : Created new [FIX/FAST] log storage with file name "<path to file>/<storage file name with timestamp>"

Description or root cause

The option for storage type is not set so the most efficient storage type (PersistentMM) is usedThis message appears when FIX Antenna creates new log message storage.

Solution or troubleshooting steps

Make sure that the storage type is specified correctly. Check if there are spaces between the property and its value.

...

This message doesn't indicate an issue, just informs that the task was finished.

LogDirectory property was specified with a non-existent path

<Timestamp>   INFO    [Engine]  <thread> Session <sender, target> : CreatedPath new [FIX/FAST] log storage with file name "<path to file>/<storage file name with timestamp>"<location> doesn't exist. Trying to create it.

Description or root cause

This message appears when FIX Antenna creates new log message storage message appears when the LogDirectory property was specified with the non-existent path for the FIX session.

Solution or troubleshooting steps

This message doesn't indicate an issue, just informs that the task was finished can be ignored. To use the particular existing log directory user must change the value of the LogDirectory property for the FIX session.