I'm trying to run this example (https://developers.refinitiv.com/elektron/elektron-sdk-cc/learning?content=26452&type=learning_material_item), but I've facing issues to run it.
Follows bellow LoggerMsg:
Text: Received ChannelDownReconnecting event on channel Channel_1
Instance Name Consumer_1_1
Error Id -1
Internal sysError 0
Error Location D:\Jenkins\workspace\ESDKCore_RCDEV\OS\VS150-64\rcdev\source\esdk\Cpp-C\Eta\Impl\Reactor\rsslReactorWorker.c:1304
Error Text Initialization timed out.
I'm using to run that example:
- Windows 10
Could you please help me find out what I'm doing wrong?
Are you using the TRCC sample code as is, without modifications?
Do you have TRCC credentials and a valid instrument and fields which you are allowed to contribute to?
Is your EMA Config file using the ChannelType::RSSL_ENCRYPTED and host pointing to the right TRCC server?
Greetings! Not sure if original poster had resolved issue, however I have the same error. When we were testing Elektron trial TCP connection this summer, we were not specifying any channel type, and loading no EmaConfig.xml file. It was enough just to create consumer like
And then call ommConsumer->registerClient specifying service name and instrument (or set of instruments to subscribe).
It was working for trial, and it is not working for Cloud, if I provide machine ID as username, and host:port received from cloud endpoint discovery. What could be the key here? Is there any option to specify channel type without EmaConfig.xml ? I see something like this in the 421_MP_ProgrammaticCfg example, however it contains too much options, and I'm not sure what are required, what are not.
Could it be just issue with requested service name?
If I use EmaConfig.xml from Elektron SDK, and set "Consumer_4" (which, according to example 113_MP_SessionMgmt, selects RSSL_SOCKET), output is the same.