Page Comparison

...

• FIX protocol version in the message differs from the one in the session

  Code Block
  language bash
  Cannot send the given message: the version of the message is <FIX version 1>, whereas session's version is <FIX version 2>.

  Description: The FIX protocol version in the message differs from the one in the session. Except the FIXT 1.1.
  

...

• 
  

  Info
  The first found error during validation is written in the <SessionRejectReason>(373) field in Reject (3) message. The rest of found errors are enumerated in the <Text>(58) field in addition if any.

Parsing errors

All the parsing errors that prevent the work proceeding are not collected at all and reported immediately when occur.

...

• The wrong tags positions in the message - outside an expected repeating group

  Code Block
  language bash
  Tag 55 is on a wrong level. This tag must be in group with leading tag: 146. Parsing stopped at column: 126 at tag 55 in message V with sequence number 2.

  Description: Valid value is in the <SessionRejectReason> (373) field in case of parsing error. Detailed error description is in the <Text> (58) field in case of parsing error. A Reject message is received with <SessionRejectReason> = "Tag specified out of required order" (373=14).

• Inconsistency between the

  number of entries in the repeating group

  declared and the

  declared number

  expected numbers of entries

  expected

  in

  a

  the repeating group

  .

  Code Block
  language bash
  Session <ESVR, GTF> : Parse Error : Incorrect NumInGroup count for repeating group (tag 78). Declared entries count: 2. Entries count in fact: 1. Parsing stopped at column: 188 in tag N/A in message D with sequence number <2>.

  Description: A Reject message has the tag SessionRejectReason (373) equaled to <Incorrect NumInGroup count for repeating group> (16) if a repeating group has an incorrect number of tags.

...