Page tree
Skip to end of metadata
Go to start of metadata


In this article, you can find a description of errors, warnings, debug, and information messages which may be spotted in FIXEdge log files.


  • Tag not defined for this message type

    <Timestamp>    ERROR    [Engine]  Session <Session_Name>; Parse Error : Tag not defined for this message type. Parsing stopped at column: *** [RefSeqNum: **, RefTagID: **, RefMsgType: **].

    Description: It means that FIXEdge received a FIX message that contains a tag [RefTagID], which is not described in FIX dictionaries for this type of message. Also, it may mean that tag [RefTagID] is outside the repeating group while in the dictionary this tag is inside the repeating group or vice versa. The exact message can be identified by its sequence number [RefSeqNum].

    Troubleshooting steps: Get the FIX message itself from <session>.in file (use RefSeqNum value for assistance). Check the corresponding FIX dictionary to validate the correctness of the error. Contact counter-party to resolve the issue or describe this custom tag in the corresponding FIX dictionary.

  • Message cannot be sent

    <Timestamp>    ERROR    [CC_Layer]  LayerImpl::sendMessage2ClientId() has failed: Message cannot be sent: client TestSMTPClient is not logged in.

    Description: This message occurs when there is an attempt to send a message to a not initialized ("logged in") Client of Transport Adapter (TA). The disclosed in log record "client" name represents the name of TA Client in

    Depending on TA type, the Client may be also referred to as "Session". For example, Clients of SMTP TA are listed under TransportLayer.SmtpTA.SMTPSessions parameter.

    The reason for this is that specific TA, to which the Client belongs, is not added to the list of enabled adapters TransportLayer.TransportAdapters in Once added, you will see in log (after FIXEdge restart) record like

    <Timestamp>   INFO    [CC_Layer]  Client TestSMTPClient has logged in

    Troubleshooting steps: 1. First of all, review BL_Config.xml file for the Rule, that routes messages to mentioned Client, and check if it is correct and does what is required by your system. Remove the Rule if there is no need in it.
    For instance, the ERROR in this specific example was caused by default BL Rule which was left unintentionally in place:

    		<FixSession SenderCompID=".*" TargetCompID=".*"/>
    		<EqualField Field="35" Value="C"/>
    			<Client Name="TestSMTPClient"/>

    2. Check that corresponding TA client was successfully started and connected. Check for correctness, especially that TA is added to TransportLayer.TransportAdapters list.

  • The connection association got dropped by a network device (NAT/router/switch)

    <Timestamp>    ERROR    [Engine] <Thread ID> New incoming connection from :0 was rejected because of the error during processing: getpeername. Transport endpoint is not connected. (Error code = 107)

    Description: The record means that there had been connection attempt from a counterparty, and when FIX Engine was trying to detect its source ip/port with getpeername function, the connection association got dropped by a network device (NAT/router/switch).

    Troubleshooting steps: reconnect the session.

  • New incoming connection was rejected

    <Timestamp>    ERROR    [Engine]  New incoming connection from was rejected because of the error during processing: Connection::receive(), EOF from

    DescriptionThis error occurs when a network device drops connection association, or there is a code issue resulting FIX connection to be terminated unexpectedly without Logouts exchange.

    Troubleshooting steps: Contact your counter-party for explanation from their side and related events that make bring more light on the root cause.

  • Error during processing Logon message

    <Timestamp>    ERROR    [Engine]  Session <Session_Name> : Error during processing Logon message from Incoming connection is rejected by application: Cannot create session. Reason: Authentication is failed or session is not configured to accept connection

    Description: This is related to setup with LDAP authentication. Authentication is performed against Session identifier  (SenderCompID and TrargetCompID) and LDAP using the Username (tag 553) and Password (tag 554) from FIX Logon message.

    Troubleshooting steps:
    1. Work with the counterparty to make sure that that supplied in Logon credentials are correct.
    2. Check if credentials are correct in LDAP and any other issues with LDAP itself.
    3. Review and check the LDAPAuthenticate section in the BL_Config.xml file.

  • Unable to establish connection (Error code = 10060)

    <Timestamp>    ERROR    [Engine]  Session <Session_Name> : Unable to establish connection: connect() to ( failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (Error code = 10060)

    Description: This is related to an address or a port of destination are not available from the host machine.

    Troubleshooting steps

    1. Use telnet to check the connection. Fix network issues.
    2. Make sure that the counterparty sees the connect attempts.
    3. Once the network has been configured and the node has become available, try to connecting again.


  • No OnActionFail is specified for rule

    <Timestamp>    DEBUG    [BL_RoutingTable]  No OnActionFail is specified for rule for 'Rule_Name'.

    Description: These messages usually indicate that you have a routing Rule, but haven’t specified what will happen if the Rule fails.

    Troubleshooting steps: These are not errors, just indications that <OnActionFail> condition might be also set up.


  • The telecommunication link error was detected

    <Timestamp>    WARN    [Engine]  Session <Session_Name> : the telecommunication link error was detected (Connection::receive(), EOF).

    Description: It means that the TCP connection was terminated unexpectedly by counter-party, without Logouts exchange.

    Troubleshooting steps: Contact counter-party and query them for sanity of their FIX adaptor/engine.

  • "MessageStorageType storageType" parameter is deprecated

    <Timestamp>    WARN    [Engine]  Session <Session_Name> : FixEngine::CreateSession(...) "MessageStorageType storageType" parameter is deprecated. Please use SessionExtraParameters::storageType instead.

    DescriptionWe improve the API of our products continuously and some parameters were left for backward compatibility. Such a message can appear in the log file in case of using non-default values for such parameters but if the value passes all checks then there is just such a record in the log file and it doesn’t affect anything.

    Troubleshooting steps: You can ignore these messages.

  • Session was created in danger mode

    <Timestamp>    WARN    [Engine]  Session <Session_Name> : session was created in danger mode - it does not use persistent message storage.

    DescriptionIt means that a session uses the transient storage, i.e. no log files with FIX messages will be created.

    Troubleshooting steps: In file you can turn on logging for a session by setting 'FixLayer.FixEngine.Session.<SessionName>.StorageType = persistentMM' (or persistent). For Admin Session (a session between FIXEdge and FIXICC Agent) you need to change the property Monitoring.AdminSession.AdminClient.StorageType (which is in file) accordingly, but we don’t recommend to do this for Admin Session - there will be quite a lot of messages.

  • Garbled message

    <Timestamp>    WARN    [Engine]  Garbled message: <FIX_Message>

    Description: The FIX Protocol takes the optimistic view; it presumes that a garbled message is received due to a transmission error rather than a FIX system problem. Therefore, if a Resend Request is sent the garbled message will be re-transmitted correctly. If a message is not considered garbled then it is recommended that a session level Reject message be sent.

    What constitutes a garbled message:
    • BeginString (tag #8) is not the first tag in a message or is not of the format 8=FIX.n.m.
    • BodyLength (tag #9) is not the second tag in a message or does not contain the correct byte count.

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

  • Parse Error : Incorrect size of repeating group.

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

    Description: This error will occur if the validation option 'verifyRepeatingGroupBounds' is enabled and FIX Engine receives a message with an incorrect repeating group size. In this case, the FIX message will be rejected.

    Before FIX Engine version 2.28.1 (and FIXEdge version 6.11.0), this parameter was always enabled.
    Troubleshooting steps: To revert this parameter after updating to the versions stated above, this parameter should be set to false. Additionally, for FIX Engine, the field Engine::SessionExtraParameters::ValidationParameters::verifyRepeatingGroupBounds_ should be set to false.


  • 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: This message appears when the session was terminated by Logout and IntradayLogoutTolerance mode is enabled. This mode means that during 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).

    Troubleshooting steps: This 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: 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.

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

  • The backup session has the same parameters as the primary session

    <Timestamp>    INFO    [Engine]  Session <Session_Name> : The backup session has the same parameters as the primary session.

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

    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.

  • A FIX Session storage type isn't specified

    <Timestamp>   INFO    [Engine]  <thread> Session property 'Session.TESTSESSION.StorageType' is not found. PersistentMM storage type is used.

    Description: The option for storage type is not set so the most efficient storage type (PersistentMM) is used.

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

  • No labels