[EMA C++] State: Closed / Suspect / Not entitled / 'A21: A required argument was NULL

cdefusco

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?

nick.zincone

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.