EZD testclient command execution error
Tried executing
rmdstestclient -S ELEKTRON_DD -il MRN_STORY -md 33 -X -v -u USERNAME
and faced below error
Service: ELEKTRON_DD ConnectionType: rssl ServerHostname: localhost SipcVersi
on: 4
Number of Connection Count = 1
Creating RSSL connection Host: localhost Port: 14002
rsslInitChannel() returned -1, Error <......\Ripc\Impl\ripcsrvr.c:5208> ripcCo
nnecting() Error: 1002 client connect() failed. System errno: (10057)
could you please suggest what needs to be done here
Best Answer
-
Hello @hemalata.gavade
Would you like to consume MRN_STORY?
If yes, rmdstestclient cannot be used. Data of News Text Analytics domain(33) is compressed using zlib prior to splitting into fragments (if required). To consume News Text Analytics data i.e. MRN_STORY, a consumer needs to re-assemble the fragments and unzip the completed buffer(data) before it can be used. Unfortunately, rmdstestclient does not perform this that’s why rmdstestclient cannot be used to consume MRN_STORY.
Anyway, you can use the following example application to get MRN_STORY:
- RFA.NET Tutorial 8 - Request and Decode Machine Readable News
- NewsAnalytics Streaming Example (MRN) under ELEKTRON SDK - JAVA - SAMPLE APPS of EMA Java API. Please refer to ExampleMRNConsoleEMAJava.md how to run the example.
- EMA Java API tutorial: EMA Consumer - Request & Decode Machine Readable News
- EMA C++ API tutorial: EMA Consumer - Request & Decode Machine Readable News
Your rmdstestclient command does not specify the server(-h <server hostname>) and port(-p <server port number) so rmdstestclient tries to connect to localhost(the default hostname) at port 14002(the default port). If EZD is not running on the localhost at port 14002, the error is shown. Please check EZD if it is running properly.
Hope this help.
0
Answers
-
Winsock error 10057 is "Socket is not connected.". I got the same error code if the port 14002 is not listening on the machine.
First, you need to verify the ezd.log in order to make sure that it runs properly. Then, you can use "netstat -anb" command to verify if the TCP port 14002 is used by the EZD process.
To verify the problem, please share the ezd.log and output from the "netstat -anb" command.
0 -
EZD is running on local host.
0 -
Hello @hemalata.gavade
To be able to investigate the problem, Please do following @jirapongse.phuriphanvichai 's answer.
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 中文论坛