Problem in Logon.

, ,
1

Imported from previous forum

2

Hi all! I am sending a Logon message to a FIX server. This is the first message in the session, therefore the sequence number is set to 1 as indicated in tag 34. However, I am receiving a null continuously. Isnt it that the first message should be a Logon message? or am i missing something else? There is no encrypt method.

8=FIX.4.19=7335=A49=PHX5056=COES5034=150=MYCLIENT52=20040218-10:49:45108=398=010=243

SenderCompId (Tag49) and TargetCompId(Tag56) are checked and are correct. The SenderSubId(Tag50) is just used by the FIX server for identification. The value written in this tag is also verified and is correct.

Any help is highly appreciated.

3

[ original email was from Ian Orford - ian.orford@ubs.com ]
On the face of it, your message looks fine - although a heartbeat interval of 3 is pretty small - 30, 60 or 120 may be more suitable.

I guess you really need to talk to the recipient of the login message - they should be able to tell you whether they can see the message and also if they don’t like it, what the problem is.

If the recipient is another test server of yours, you may need to setup the sessions. An engine will normally need to be told to expect a login from a given CompID. Perhaps this is a configuration issue.

> Hi all! I am sending a Logon message to a FIX server. This is the first message in the session, therefore the sequence number is set to 1 as indicated in tag 34. However, I am receiving a null continuously. Isnt it that the first message should be a Logon message? or am i missing something else? There is no encrypt method.
>
> 8=FIX.4.19=7335=A49=PHX5056=COES5034=150=MYCLIENT52=20040218-10:49:45108=398=010=243
>
> SenderCompId (Tag49) and TargetCompId(Tag56) are checked and are correct. The SenderSubId(Tag50) is just used by the FIX server for identification. The value written in this tag is also verified and is correct.
>
> Any help is highly appreciated.
>