Python EIkon API - Getting 503 errors for the last three days. Anyone else seeing this?

For the last three days I've consistently been hitting 503 errors when trying to pull data using the Python Eikon API. Anyone else seeing this? If this is a known issue, could someone please reply with the post from Reuters?
Best Answer
-
Hi @willis.kidd, @m.iyongo We have the following update that may or may not be relevant as we don't know your versions etc. We had another 503 error that was investigated by our dev team and here follows the advice from them:
He was able to reproduce the issue with same versions (Desktop 4.0.52055 + PROXY (9.52.0.51). But once he removed Eikon (and all related directories like user cache) then reinstalled it, now it's working well. Further, he wasn’t able to come back to the initial status to reproduce the issue. He thinks that’s linked to the way that Eikon is updated and/or upgraded.
Something that causes the issue could persist in Eikon cache (or elsewhere). We have forwarded to the Eikon Team to investigate further but in the interim the tests/steps are as follows:1. Clean Eikon cache, then retry.
2. Reboot the machine then retry.
3. Uninstall Eikon (check that "C:\Program Files (x86)\Thomson Reuters" and "C:\Users\<username>\AppData\Local\Thomson Reuters\Eikon User" was suppressed or are empty), then reinstall Eikon.
I'm sorry if the third option is quite radical, but I don't see another one.
I hope this can help.
0
Answers
-
See the discussion on the following thread.
There's at least one more user experiencing 503 error, which is being investigated. However based on the info available in your post we cannot be certain whether the issue you experience is similar to the one detailed on the above thread. Would you mind providing the details of the symptoms you experience? Have you tried restarting Eikon application? When restarting Eikon, make sure all Eikon processes are gone from Windows Task Manager after Eikon shutdown and before starting it up.
0 -
I have not tried restarting Eikon. I'll go ahead and try that now.
The post you've linked doesn't resolve though.0 -
I have the same problem
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 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
- 252 ETA
- 556 WebSocket API
- 38 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
- 652 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛