Logon failed

Imported from previous forum

Hi!

I am a newbie and I am using FIX 4.2 version.
I tried to connect to a FIX engine with my client and I am disconnected as soon as I initiate a Logon. Both parts (initiator and acceptor) reset our sessions and tried again, but we have still the problem.
When I look at the logs, I have:
"8=FIX.4.29=7335=A34=149=MOMENTUM52=20040429-14:48:41.00056=DBAGFIPLUS98=0108=3010=076" in my outgoing log, and
"8=FIX.4.29=006935=A34=149=DBAGFIPLUS56=MOMENTUM52=20040429-14:46:1098=0108=3010=237" in my incoming log.
I am the initiator of the session, it seems that I send a Logon message and have a Logon message back. The sequence numbers seem ok (value 1), but unfortunately I am disconnected.
The only weird thing is the 2min gap in the sending time tags (#52), as only few seconds happened.
Did someone ever meet this problem?

Renaud

> When I look at the logs, I have:
> "8=FIX.4.29=7335=A34=149=MOMENTUM52=20040429-14:48:41.00056=DBAGFIPLUS98=0108=3010=076" in my outgoing log, and
> "8=FIX.4.29=006935=A34=149=DBAGFIPLUS56=MOMENTUM52=20040429-14:46:1098=0108=3010=237" in my incoming log.
> I am the initiator of the session, it seems that I send a Logon message and have a Logon message back. The sequence numbers seem ok (value 1), but unfortunately I am disconnected.

> The only weird thing is the 2min gap in the sending time tags (#52), as only few seconds happened.
> Did someone ever meet this problem?

Check the time on the two machines that the engines are on they might not be synched very well

Dont know why you are disconnecting - this is probably a setup problem with the sessions

>
> Renaud
>

[ original email was from Jeremy Sutton - jezza.sutton@patsystems.com ]
I suspect the difference in the times is causing one side or other to consider the messages stale. I have found my FIX libraries can do this if the message timestamps are too far apart - and the default in my libraries was 10s so I saw it quite a bit until we changed the value.

You should probably ensure that both systems are running NTP and are synchronized to a known accurate time source.