{{Quickfixn}} Tag appears more than once

Grant Birchmeier gbirchmeier at connamara.com
Tue Mar 10 08:25:04 PDT 2020


"Tag appears more than once: 1" refers to the Account tag (e.g. "1=SG S835
ABC2").

This means that 1 is the first tag that it thinks is not part of the
repeating group.  (The message means that the parser thinks it's finding
the tag outside of a group.)

Oh-- oops, my indents were slightly wrong in my previous message.  This is
the correct version:

552=2   NoSides
  54=1    Side
    1427=1063399             SideExecID
    1005=DualTrade01_S835B   SideTradeReportID

    453=4           NoPartyIDs  (Component 'Parties')
      448=S835        PartyID
        447=D         PartyIDSource
        452=7         PartyRole
      448=ABCGroup
        447=D
        452=1
      448=S835
        447=D
        452=4
      448=SGX
        447=D
        452=21

    1=SG S835 ABC2    Account (FIXED INDENT: inside 54 group, after 543
group)
    578=FIX           TradeInputSource
    336=1             TradingSessionID
    625=3             TradingSessionSubID
    1057=N            AggressorIndicator
    2344=3            SideRiskLimitCheckStatus


On Tue, Mar 10, 2020 at 10:13 AM Veduruparthi Raju <rveduruparthi at gmail.com>
wrote:

> I have further looked into it and looks the the quickfix is not able to
> recognize the tag 552 (NoSidesGroup) as a repeating group, thus failing
> with the error "Tag appears more than once:1 ". I have made sure the
> NoSidesGroup is part of the repeating group too.
>
> I have compared the FIX schema with ICE( FIX44) and SGX (currently i am
> working on with FIX5.0SP2)  and looks like ICE always have the tag 552
> value as 1 and hence i have no issues with the  ICE messages. However the
> SGX FIX messages always have the tag 552 value as 2 and these messages are
> failing.
>
> I am stuck now and was just wondering if there is any workaround for this ?
>
> 8=FIXT.1.1 9=658 35=AE 34=13 49=TITANOTC 52=20200310-14:56:40.089
> 56=IONGROUP 57=IONFIXTRADER 15=USD 17=66345 31=181 32=5 55=ACFH20
> 60=20200305-03:47:00 75=20200305 150=F 423=2 568=1
> 571=23df851d-4d3d-4a04-a4b5-526b0bb56045 715=20200305 748=13 828=1 854=1
> 912=N 1003=74755 1300=Commodities 2343=3 552=2 54=1 1427=1054939 453=5
> 448=S835 447=D 452=7 448=S835All 447=D 452=36 448=IONGROUP 447=D 452=1
> 448=S835 447=D 452=4 448=SGX 447=D 452=21 1=SG S835 ION2 578=GUI 336=1
> 625=3 1057=N 2344=3 54=2 1427=1054938 453=5 448=S835 447=D 452=7
> 448=S835All 447=D 452=36 448=IONGROUP 447=D 452=1 448=S835 447=D 452=4
> 448=SGX 447=D 452=21 1=SG S835 ION1 578=GUI 336=1 625=3 1057=N 2344=3
> 10=234
>
>
> 8=FIXT.1.1 9=116 35=3 34=14 49=IONGROUP 52=20200310-14:56:41.309
> 56=TITANOTC 45=13 58=Tag appears more than once 371=1 372=AE 373=13 10=069
>
>
> Thanks,
> --Raju.v
>
> On Fri, Mar 6, 2020 at 3:08 PM Veduruparthi Raju <rveduruparthi at gmail.com>
> wrote:
>
>> Hi Grant,
>>
>> I digged down the XML and the everything seems to be inline except two
>> custom tags for the message type AE, one is part of the NoSides group(2344)
>> and other tag (2343) is part of the TradecaptureReport. so i have added
>> those two tags(2343 ,2344) and i still see the same error.
>>
>> I ran out of thoughts and could not figure out the issue. Appreciate your
>> help on this.
>>
>> The below is the FIX message and response. I also have attached the
>> FIX50SP2.xml schema for your reference.
>>
>> 8=FIXT.1.1 9=654 35=AE 34=2 49=ABCOTC 52=20200306-20:57:41.460
>> 56=ABCGROUP 57=ABCFIXTRADER 15=USD 17=66359 31=1.41 32=110 55=ACFH20
>> 60=20200306-02:03:29 75=20200306 150=F 423=2 568=1
>> 571=130f4027-9265-4b0e-be6b-d55ff62374ec 715=20200306 748=4 828=1 854=1
>> 912=N 1003=74770 1300=Commodities 2343=3 552=2 54=1 1427=1063399
>> 1005=DualTrade01_S835B 453=4 448=S835 447=D 452=7 448=ABCGroup 447=D 452=1
>> 448=S835 447=D 452=4 448=SGX 447=D 452=21 1=SG S835 ABC2 578=FIX 336=1
>> 625=3 1057=N 2344=3 54=2 1427=1063398 1005=DualSide01_S835A 453=4 448=S835
>> 447=D 452=7 448=ABCGroup 447=D 452=1 448=S835 447=D 452=4 448=SGX 447=D
>> 452=21 1=SG S835 ABC1 578=FIX 336=1 625=3 1057=N 2344=3 10=252
>>
>>
>> 8=FIXT.1.1 9=114 35=3 34=3 49=ABCGROUP 52=20200306-20:57:41.567 56=ABCOTC
>> 45=2 58=Tag appears more than once 371=1 372=AE 373=13 10=232
>>
>> Thanks,
>> --Raju.v
>>
>> On Fri, Mar 6, 2020 at 10:09 AM Veduruparthi Raju <
>> rveduruparthi at gmail.com> wrote:
>>
>>> Thanks Grant.. i do think the same. Let me compare the DD and message
>>> and will see if i can find any.
>>>
>>> Thanks,
>>> --Raju.v
>>>
>>> On Fri, Mar 6, 2020 at 9:48 AM Grant Birchmeier <
>>> gbirchmeier at connamara.com> wrote:
>>>
>>>> "I have reached out to my counterparty and have checked with them if
>>>> they use any customized version of dictionary and they came back saying no."
>>>>
>>>> I *guarantee* you that this is wrong.  They've changed something.
>>>> Maybe in this message or maybe not, but I cannot believe they are using a
>>>> completely unmodified DD.
>>>>
>>>> In 10 years of working with FIX, I've never worked with a commercial
>>>> counterparty that hasn't deviated from the standard DD at least a little
>>>> bit.
>>>>
>>>> Have a look at your message and your DD and see what you can find.  If
>>>> you're still stuck, let us know.
>>>>
>>>> -Grant
>>>>
>>>>
>>>> On Fri, Mar 6, 2020 at 8:37 AM Veduruparthi Raju <
>>>> rveduruparthi at gmail.com> wrote:
>>>>
>>>>> Thank you both.
>>>>>
>>>>> I have reached out to my counterparty and have checked with them if
>>>>> they use any customized version of dictionary and they came back saying no.
>>>>> Looks like i need to dig down the FIx schema to figure out the issue.
>>>>> But from the initial looks the data seems to be in sync with the schema.
>>>>> The below is the data for your reference and i am using the
>>>>> standard FIX5.0SP2.xml schema which came with FIX version 1.9 download.
>>>>>
>>>>> 8=FIXT.1.1
>>>>> 9=656
>>>>> 35=AE
>>>>> 34=2
>>>>> 49=ABCOTC
>>>>> 52=20200305-04:21:15.163
>>>>> 56=TestGroup
>>>>> 57=TestTrader
>>>>> 15=USD
>>>>> 17=66345
>>>>> 31=181
>>>>> 32=5
>>>>> 55=ACFH20
>>>>> 60=20200305-03:47:00
>>>>> 75=20200305
>>>>> 150=F
>>>>> 423=2
>>>>> 568=1
>>>>> 571=4d89077f-c032-4793-8e26-c2ce18f85cb3
>>>>> 715=20200305
>>>>> 748=2
>>>>> 828=1
>>>>> 854=1
>>>>> 912=N
>>>>> 1003=74755
>>>>> 1300=Commodities
>>>>> 2343=3
>>>>> 552=2
>>>>> 54=1
>>>>>  1427=1054939
>>>>>  453=5
>>>>>  448=S835
>>>>> 447=D
>>>>> 452=7
>>>>>  448=S835All
>>>>> 447=D
>>>>> 452=36
>>>>>  448=TestGroup
>>>>> 447=D
>>>>> 452=1
>>>>>  448=S835
>>>>> 447=D
>>>>> 452=4
>>>>>  448=SGX
>>>>> 447=D
>>>>> 452=21
>>>>> 1=SG S835 ABC2
>>>>> 578=GUI
>>>>> 336=1
>>>>> 625=3
>>>>> 1057=N
>>>>> 2344=3
>>>>>
>>>>> 54=2
>>>>>  1427=1054938
>>>>>  453=5
>>>>>  448=S835
>>>>> 447=D
>>>>> 452=7
>>>>>  448=S835All
>>>>> 447=D
>>>>> 452=36
>>>>>  448=IONGroup
>>>>> 447=D
>>>>> 452=1
>>>>>  448=S835
>>>>> 447=D
>>>>> 452=4
>>>>>  448=SGX
>>>>> 447=D
>>>>> 452=21
>>>>>  1=SG S835 ABC1
>>>>>  578=GUI
>>>>>  336=1
>>>>>  625=3
>>>>>  1057=N
>>>>>  2344=3
>>>>>
>>>>> 10=112
>>>>>
>>>>> Thanks,
>>>>> --Raju.v
>>>>>
>>>>> On Thu, Mar 5, 2020 at 2:40 PM Mike Gatny <mgatny at connamara.com>
>>>>> wrote:
>>>>>
>>>>>> On Thu, Mar 5, 2020 at 3:26 PM Grant Birchmeier <
>>>>>> gbirchmeier at connamara.com> wrote:
>>>>>>
>>>>>>> 1) Get ahold of your counterparty's documentation, and edit your
>>>>>>> FIX50SP2.xml file to match the changes that it's made in their dictionary.
>>>>>>>
>>>>>>
>>>>>> You can also ask them if they have a quickfix-compatible data
>>>>>> dictionary xml that they can share with you.  Quite a few do have one.
>>>>>>
>>>>>> --
>>>>>> Mike Gatny
>>>>>> Connamara Systems
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> 2) If you're ever stumped, then consult your FIX50SP2.xml file and
>>>>>>> manually parse the message that's being rejected.  You'll find the mismatch.
>>>>>>>
>>>>>>> -Grant
>>>>>>>
>>>>>>> On Thu, Mar 5, 2020 at 2:02 PM Veduruparthi Raju <
>>>>>>> rveduruparthi at gmail.com> wrote:
>>>>>>>
>>>>>>>> Ok.. i have changed the configuration file to NOT to use the
>>>>>>>> DataDictionary key, instead to use the AppDataDictionary key and i still
>>>>>>>> see the same "Tag appears to be more than once"
>>>>>>>> The below is my updated config file
>>>>>>>>
>>>>>>>>   # default settings for sessions
>>>>>>>>   [DEFAULT]
>>>>>>>>   ConnectionType=initiator
>>>>>>>>   ReconnectInterval=60
>>>>>>>>   SenderCompID=XXXXX
>>>>>>>>   SenderSubID=XXXXX
>>>>>>>>   FileLogPath=c:\logs\
>>>>>>>>   FileStorePath=c:logs\
>>>>>>>>   #UseDataDictionary=Y
>>>>>>>>   #ValidateFieldsOutOfOrder=N
>>>>>>>>   HeartBtInt=30
>>>>>>>>   SocketConnectPort=42425
>>>>>>>>   SocketConnectHost=localhost
>>>>>>>>   StartTime=00:00:00
>>>>>>>>   EndTime=00:00:00
>>>>>>>>   LogonTimeout=60
>>>>>>>>
>>>>>>>>   [SESSION]
>>>>>>>>   BeginString=FIXT.1.1
>>>>>>>>   TargetCompID=XXXXXX
>>>>>>>>   UseDataDictionary=Y
>>>>>>>>   ValidateFieldsOutOfOrder=N
>>>>>>>>   TransportDataDictionary=C:\FIXT11.xml
>>>>>>>>   AppDataDictionary.FIX5.0SP2=C:\FIX50SP2.xml
>>>>>>>>   ResetOnDisconnect=Y
>>>>>>>>   CheckLatency=N
>>>>>>>>   DefaultApplVerID=9
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> --Raju.v
>>>>>>>>
>>>>>>>> On Thu, Mar 5, 2020 at 1:11 PM Veduruparthi Raju <
>>>>>>>> rveduruparthi at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> I am developing an application which uses FIX version 1.9 /
>>>>>>>>> FIXSP5.0SP2 and when i am receiving the trade messages, the messages get
>>>>>>>>> rejected with the message saying "Tag appears more than once" for the tag 1
>>>>>>>>> (Account) , the below is the log.
>>>>>>>>>
>>>>>>>>> 58=Tag appears more than once 371=1 372=AE 373=13 10=218
>>>>>>>>>
>>>>>>>>> So looks like is not recognizing the repeating groups.
>>>>>>>>> I am using the DataDictionary,  TransportDataDictionary keys in
>>>>>>>>> the setting file pointing to the schema files.
>>>>>>>>> Also using   UseDataDictionary=Y and   ValidateFieldsOutOfOrder=N
>>>>>>>>> keys.
>>>>>>>>> But still am getting the same error.
>>>>>>>>>
>>>>>>>>> I read in the documentation somewhere to use the AppDataDictionary
>>>>>>>>> key when you use FIXT1.1, so when i used it pointing to the schema file
>>>>>>>>> then it errors out with "Tag not defined"
>>>>>>>>>
>>>>>>>>> Any advise how to get rid of that error
>>>>>>>>>
>>>>>>>>> The below is my QuickFix settings file configuration.
>>>>>>>>>   # default settings for sessions
>>>>>>>>>   [DEFAULT]
>>>>>>>>>   ConnectionType=initiator
>>>>>>>>>   ReconnectInterval=60
>>>>>>>>>   SenderCompID=XXXXXX
>>>>>>>>>   SenderSubID=XXXXX
>>>>>>>>>   FileLogPath=c:\logs\
>>>>>>>>>   FileStorePath=c:\logs\
>>>>>>>>>   UseDataDictionary=Y
>>>>>>>>>   ValidateFieldsOutOfOrder=N
>>>>>>>>>   HeartBtInt=30
>>>>>>>>>   SocketConnectPort=42425
>>>>>>>>>   SocketConnectHost=localhost
>>>>>>>>>   StartTime=00:00:00
>>>>>>>>>   EndTime=00:00:00
>>>>>>>>>   LogonTimeout=60
>>>>>>>>>
>>>>>>>>>   [SESSION]
>>>>>>>>>   BeginString=FIXT.1.1
>>>>>>>>>   TargetCompID=TITANOTC
>>>>>>>>>   DataDictionary=C:\FIX50SP2.xml
>>>>>>>>>   TransportDataDictionary=C:\FIXT11.xml
>>>>>>>>>   #AppDataDictionary=C:\FIX50SP2.xml
>>>>>>>>>   ResetOnDisconnect=Y
>>>>>>>>>   CheckLatency=N
>>>>>>>>>   DefaultApplVerID=9
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> --Raju.v
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks,
>>>>>>>> --Raju.v
>>>>>>>> _______________________________________________
>>>>>>>> Quickfixn mailing list
>>>>>>>> Quickfixn at lists.quickfixn.com
>>>>>>>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Grant Birchmeier
>>>>>>> *Connamara Systems, LLC*
>>>>>>> *Made-To-Measure Trading Solutions.*
>>>>>>> Exactly what you need. No more. No less.
>>>>>>> http://connamara.com
>>>>>>>
>>>>>>> This email, along with any attachments, is confidential. If you
>>>>>>> believe you received this message in error, please contact the sender
>>>>>>> immediately and delete all copies of the message. Thank you from Connamara
>>>>>>> Systems, LLC._______________________________________________
>>>>>>> Quickfixn mailing list
>>>>>>> Quickfixn at lists.quickfixn.com
>>>>>>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>>>>>>
>>>>>>
>>>>>> This email, along with any attachments, is confidential. If you
>>>>>> believe you received this message in error, please contact the sender
>>>>>> immediately and delete all copies of the message. Thank you from Connamara
>>>>>> Systems, LLC._______________________________________________
>>>>>> Quickfixn mailing list
>>>>>> Quickfixn at lists.quickfixn.com
>>>>>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> --Raju.v
>>>>> _______________________________________________
>>>>> Quickfixn mailing list
>>>>> Quickfixn at lists.quickfixn.com
>>>>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>>>>
>>>>
>>>>
>>>> --
>>>> Grant Birchmeier
>>>> *Connamara Systems, LLC*
>>>> *Made-To-Measure Trading Solutions.*
>>>> Exactly what you need. No more. No less.
>>>> http://connamara.com
>>>>
>>>> This email, along with any attachments, is confidential. If you believe
>>>> you received this message in error, please contact the sender immediately
>>>> and delete all copies of the message. Thank you from Connamara Systems, LLC.
>>>> _______________________________________________
>>>> Quickfixn mailing list
>>>> Quickfixn at lists.quickfixn.com
>>>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>>>
>>>
>>>
>>> --
>>> Thanks,
>>> --Raju.v
>>>
>>
>>
>> --
>> Thanks,
>> --Raju.v
>>
>
>
> --
> Thanks,
> --Raju.v
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com

-- 
This email, along with any attachments, is confidential. If you believe you 
received this message in error, please contact the sender immediately and 
delete all copies of the message. Thank you from Connamara Systems, LLC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20200310/f2f2a554/attachment.htm>


More information about the Quickfixn mailing list