[EMA C++] State: Closed / Suspect / Not entitled / 'A21: A required argument was NULL
We are trying to connect via EMA C++ API to an our assigned Service Name using port 14002
But we receive this error during login process on Linux:
onInvalidUsage Error[Closed / Suspect / Not entitled / 'A21: A required argument was
With the same code on a Windows machine all work fine, login process and subscriptions to RICs.
The Emalog on Linux is shown below:
loggerMsg
TimeStamp: 18:13:02.464
ClientName: EmaConfig
Severity: Error
Text: error reading configuration file [EmaConfig.xml]; file is empty
loggerMsgEnd
loggerMsg
TimeStamp: 18:13:02.464
ClientName: EmaConfig
Severity: Error
Text: failed to extract configuration from path []
loggerMsgEnd
loggerMsg
TimeStamp: 18:13:02.843
ClientName: ChannelCallbackClient
Severity: Success
Text: Received ChannelUp event on channel Channel
Instance Name Consumer_1_1
Connected component version: ads2.6.9.L1.linux.tis.rrg 64-bit
loggerMsgEnd
loggerMsg
TimeStamp: 18:13:02.877
ClientName: LoginCallbackClient
Severity: Error
Text: RDMLogin stream was closed with status message
State: Closed / Suspect / Not entitled / 'A21: A required argument was NULL
'
loggerMsgEnd
The Emalog on Windows where all work fine is shown below:
loggerMsg
TimeStamp: 18:23:34.114
ClientName: EmaConfig
Severity: Error
Text: error reading configuration file [EmaConfig.xml]; file is empty
loggerMsgEnd
loggerMsg
TimeStamp: 18:23:34.114
ClientName: EmaConfig
Severity: Error
Text: failed to extract configuration from path []
loggerMsgEnd
loggerMsg
TimeStamp: 18:23:34.300
ClientName: ChannelCallbackClient
Severity: Success
Text: Received ChannelUp event on channel Channel
Instance Name Consumer_1_1
Connected component version: ads2.6.9.L1.linux.tis.rrg 64-bit
loggerMsgEnd
What could be the problem?
Best Answer
-
Hi @cdefusco,
There are 3 up to parameters that could be used to permission users when logging in, i.e. username, position, applicationId, i.e.
Looking at your error, your server may be complaining about one of the 3, in particular, position and applicationId as these 2 do not have defaults. Both Windows and Linux should default the same but perhaps there may be an issue or slight behavior difference between the 2.
What I would do is reach out to your TREP administrator and ask them what specifically is NULL. The ADS logs should provide more details why it failed. I would also check what the complete login requirements are for you, ie. username, position and applicationID and try to set these explicitly within the OmmConsumerConfig() call.
0
Answers
-
Hi @cdefusco,
Are you explicitly specifying login credentials? Or are you using the defaults based on your desktop login? The thing that stands out to me is that if you are not specifying your login credentials, then perhaps the defaults are different between the 2 environments.
0 -
I am explicitly specifying login credentials.
In Linux using the classthomsonreuters::ema::domain::login::Login::LoginStatus
I Receive this response
StreamState[Closed]
DataState[Suspect]
StatusCode[NotAuthorized]
StatusText[A21: A required argument was NULL]0 -
I solved the problem.
It seems that on windows the applicationID is set by default to 256 as I find it in the response to the login.
On Linux, on the other hand, there is no default and therefore the parameter must be set explicitly (for example 256).
For the position (I don't know for what mechanism) but the application simply connects putting it equal to empty string.
To recap:
ApplicationID = 256;
Position = "";
In this way I connect without problems as I already connected to windows.
Thank you.0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛