Another case of RET_INVALID_DATA on LOGON
Another case of RET_INVALID_DATA on LOGON
09 Apr 2020, 16:28
Hi Team -
I've read that a few others have hit this issue - but I haven't managed to solve it myself. In short - I cannot establish my session.
On quote:
OUT > 8=FIX.4.4 | 9=141 | 35=A | 49=<broker>.<id> | 56=CSERVER | 57=QUOTE | 50=QUOTE | 34=1 | 52=20200409-13:10:57.337142 | 98=0 | 108=30 | 141=Y | 553=<id> | 554=xxxxxxxxx | 10=087 |
IN < 8=FIX.4.4 | 9=107 | 35=5 | 34=1 | 49=CSERVER | 50=QUOTE | 52=20200409-13:10:58.270 | 56=<broker>.<id> | 57=QUOTE | 58=RET_INVALID_DATA | 10=080 |
On trade:
OUT > 8=FIX.4.4 | 9=141 | 35=A | 49=<broker>.<id> | 56=CSERVER | 57=TRADE | 50=TRADE | 34=1 | 52=20200409-13:10:57.445038 | 98=0 | 108=30 | 141=Y | 553=<id> | 554=xxxxxxxxx | 10=031 |
IN < 8=FIX.4.4 | 9=107 | 35=5 | 34=1 | 49=CSERVER | 50=TRADE | 52=20200409-13:10:58.251 | 56=<broker>.<id> | 57=TRADE | 58=RET_INVALID_DATA | 10=019 |
Things I've tried to no avail:
- Both SSL and plain text
- Resetting my credentials (are there restrictions on password?)
- I've triple and quadruple checked that I'm using the correct host/port for QUOTE and TRADE (obtained from settings > advanced > FIX API)
- Disabled microsecond-timestamps temporarily
Any ideas as to what my next steps should be?
Thank you in advance!
Replies
ctid1770399
05 Jul 2020, 14:12
RE: Another case of RET_INVALID_DATA on LOGON [SOLVED]
Thank you for sharing the solution, this was very helpful.
@ctid1770399
ctid1935420
10 Apr 2020, 08:40 ( Updated at: 21 Dec 2023, 09:22 )
Another case of RET_INVALID_DATA on LOGON [SOLVED]
I've managed to solve this. Documenting the answer here for anyone else that comes across the same issue.
As other forum posts mention - RET_INVALID_DATA means an invalid password. My issue was that I wasn't aware that the FIX session password is NOT THE SAME as your general CTID password.
You can set the FIX session passwords using the "Change Password" within the FIX API settings.
@ctid1935420