Error code 500 | Server Error: {"code":500,"message":"Remote server did not reply in an a timely ...

...fashion....)
Hi community!
after the help desk referred me with my problem to this forum, would be great if one of the dev experts could have a look pls. I have checked accross previous entries but seem like this Error code 500 is a bit generic.
In eikon version 1.0.1, an error for port 9060 is thrown. Seems though missleading as that port isnt open for neither of my team but for a colleague the actual eikon lib works.
I have been using eikon libs for >4y already without greater issue. Certainly, sometimes bit instable, but no connection at all possible ...on a couple of machines...raises eyebrows with me. Seems some profile issue here maybe??
using 1.1.17 of the eikon package for Python
...lib\site-packages\eikon\json_requests.py", line 134, in send_json_request
raise EikonError(eikon_err.code, eikon_err.message)
eikon.eikonError.EikonError: Error code 500 | Server Error: {"code":500,"message":"Remote server did not reply in a timely fashion. Got no response after 60000 ms"}
ek.__version__
'1.1.17'
any help/comment appreciated
tx
Best Answer
-
Thank you for sharing this information.
The problem could be in the Eikon or Refinitiv Workspace processes, not in the Eikon Data API.
The API got this error from the API Proxy. It is beyond the scope of the API.
You contact the Eikon or Refinitiv Workspace support support team directly via MyRefinitiv to verify what the problem is.
0
Answers
-
Thank you for reaching out to us.
According to the error code (Error code 500 | Server Error), it should be the problem on the Eikon process (Eikon API Proxy) when connecting to the server. You may need to contact the Eikon support team directly via MyRefinitiv to verify what the problem is.
Does the problem happen every time or occasionally?
If it happens every time, please share the code that you are using. Therefore, I can run it on my machine.
0 -
Thanks for coming back on this.I agree, proxy server issue is the key here.
As it turns out, an upgrade to a higher version of EIKON fixed the issue now.
In the last months, I have seen it on a weekly basis that python EIKON lost the connection..only a hard restart of the whole machine (not only EIKON) allowed a
reconnection in that case. Not sure if there is some more general issue behind that? Maybe you have an idea to that seemingly related question?
tx
Bernd
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 629 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛