API Support Forum
OEC API > FIX Support > FIX server not accepting the logon request
Author Topic: FIX server not accepting the logon request
(2 messages, Page 1 of 1)
Moderators: VPfau
KIkudome
Posts: 1
Joined: Feb 10, 2017


Posted: Feb 13, 2017 @ 08:32 PM             Msg. 1 of 2
I can't connect to the FIX service ( api.gainfutures.com, port 9300). I got the "Connection reset by peer." error.

This is the FIX message my send out:
8=FIX.4.4^A9=97^A35=A^A34=2^A49=KIkudome^A52=20170214-02:27:23.924^A56=OEC_TEST^A98=0^A108=30^A553=KIkudome^A554=API#####^A10=070^A

Is there anything I missed or the account is not set up right?

Thanks

Wei
CMicciche902
Posts: 225
Joined:


Posted: Feb 14, 2017 @ 12:29 PM             Msg. 2 of 2
According to our logs, you are missing UUID tag:
\\API30CLIORD01\FIXOrderServer_Log\FIXOrderServer20170213.log
16:16:05.947 DEBUG [tid 806] - IsUserEligible: user 'FIX.4.4:OEC_TEST->KIkudome' is not eligible. SenderCompID: OEC_TEST, UUID: '', UUID required: True
20:27:23.935 DEBUG [tid 252] - IsUserEligible: user 'FIX.4.4:OEC_TEST->KIkudome' is not eligible. SenderCompID: OEC_TEST, UUID: '', UUID required: True


You may following this example: https://gainfutures.com/api/html/1e1d0ea3-3aaa-46b9-b510-9830819b1377.htm

Remember, UUID key is needed to establish connection. The Sample UUID [9e61a8bc-0a31-4542-ad85-33ebab0e4e86] may be used for testing. Once your Development is finished and you are ready for Conformance, you will receive custom UUID for your application.

Request:

8=FIX.4.4|9=114|35=A|34=1|49=username|52=20140315-18:38:39|56=OEC_TEST|98=0|108=30|554=password|12003=9e61a8bc-0a31-4542-ad85-33ebab0e4e86|10=114
Chris M