error in ADS.log is
A21: A required argument was NULL
Consumer OS: windows 10
Consumer RFA version : 7.5.1.1 (for example C++ RFA7_Common100_x64.dll)
Any ideas on how to resolve this?
regards
will
1
●0 ●0 ●2
RFA7 not connecting to ADS
1
●0 ●0 ●2
@moragodkrit Yes same ADS versions for all testing ADS 2.6 and same Dacs 6.3 version as well. Interesting how the older code would work without OMM login in the config, the fix you provided does work for the newer code. If infra is the same not sure why this was needed possibly some upstream changes to the Elektron feed?
what is OMM Login in the config?, RFA OMM does not have a configuration to set the login. Is this your own configuration?
Normally you can turn on RSSL tracing log on both versions of your application and then compare the incoming and outgoing message between RFA and Infra. It should help confirm what is the difference between two versions.
7.6k
●15 ●6 ●9
Please verify the DACS position your application send in OMM Login. I guess that your application receive the same status text, right?
The status text “A21: A required argument was NULL” generated by Infra component/ADS. It came from the new requirement in a more recent version of DACS. Now DACS requires the login position of consumer application to be in the format of "ip addr/hostname" or “ip addr/net” e.g.”192.168.1.1/net”.
You have to set valid DACS Position in the OMM Login message.
1
●0 ●0 ●2
Hi this worked great thanks, one question though.
why the old configuration and old code (without position parameter) work ok on Windows 7 and Windows 2008 R2 but NOT on Windows 10?
Are you connecting to the same version of ADS and using the same version of DACS server?
As far as I understand it's the requirement of the new version of DACS server.
1
●0 ●0 ●2
Thanks at this point we are connected up and pulling data nicely again thanks for your assistance
