Eikon Data API session hanging

jason.huang

I got a very strange problem running Eikon Data API application.

The session hangs at specific time at 12:00am. 10:00am, 12:00pm (Sydney time zone). and the session is blocked from that point.

The requests sent in these periods are normal, and they worked fine after session was restarted

The API error logs showing error like this

[2022-07-22 10:00:34,204;s] - [ERROR] - [_check_server_error] - Backend error. 400 Bad Request

[2022-07-22 10:00:34,220;s] - [ERROR] - [send_json_request] - HTTP request failed: EikonError-Backend error. 400 Bad Request

[2022-07-22 10:00:47,221;s] - [ERROR] - [send_json_request] - HTTP request failed: Set changed size during iteration

[2022-07-22 10:00:48,583;s] - [ERROR] - [send_json_request] - HTTP request failed: Set changed size during iteration

[2022-07-22 10:00:50,083;s] - [ERROR] - [_check_server_error] - Backend error. 400 Bad Request

[2022-07-22 10:00:50,101;s] - [ERROR] - [send_json_request] - HTTP request failed: EikonError-Backend error. 400 Bad Request

[2022-07-22 10:00:51,911;s] - [ERROR] - [_check_server_error] - Backend error. 400 Bad Request

[2022-07-22 10:00:51,911;s] - [ERROR] - [send_json_request] - HTTP request failed: EikonError-Backend error. 400 Bad Request

When session is blocked, the response from API shows error like this

2022-07-18 13:15:33,372 - qykit.eikondata - ERROR - eikon data api request get_data failed: Error code 401 | Eikon Proxy not running or cannot be reached. Please read the documentation on troubleshooting

2022-07-18 13:15:34,389 - qykit.eikondata - ERROR - eikon data api request get_data failed: Error code 401 | Eikon Proxy not running or cannot be reached. Please read the documentation on troubleshooting

raksina.samasiri

Hi @jason.huang ,

May I ask if you use the script to restart Eikon Desktop during the time that the error occurs?

as I saw the question posted here and the error 'Error code 401 | Eikon Proxy not running or cannot be reached. Please read the documentation on troubleshooting', the suggestion for this error was suggested by my colleague as below.

Double-check that you are running your python code on the same physical machine where your Eikon/Workspace is running. Eikon proxy is part of your desktop.

See Eikon Data API Quick Start guide for Windows on how to create your valid API Key.

If the issue persists, review article Eikon Data API(Python) Troubleshooting | Refinitiv for the steps to troubleshoot.

Hope that this information is of help

jason.huang

raksina.samasiri

Jul 25, 2022

Hi @jason.huang ,

May I ask if you use the script to restart Eikon Desktop during the time that the error occurs?

as I saw the question posted here and the error 'Error code 401 | Eikon Proxy not running or cannot be reached. Please read the documentation on troubleshooting', the suggestion for this error was suggested by my colleague as below.

Double-check that you are running your python code on the same physical machine where your Eikon/Workspace is running. Eikon proxy is part of your desktop.

See Eikon Data API Quick Start guide for Windows on how to create your valid API Key.

If the issue persists, review article Eikon Data API(Python) Troubleshooting | Refinitiv for the steps to troubleshoot.

Hope that this information is of help

I restart the Eikon at midnight 12:00am. It is up for the whole day. And the python app on Eikon Data API is running on same host, and it works fine to retrieve data other than these several specific time.

If the API key is invalid, it won't work at all. Not my case

raksina.samasiri

jason.huang

Jul 28, 2022

I restart the Eikon at midnight 12:00am. It is up for the whole day. And the python app on Eikon Data API is running on same host, and it works fine to retrieve data other than these several specific time.

If the API key is invalid, it won't work at all. Not my case

hi @jason.huang ,

I apologize for the error you've found, case number 11470349 was raised on your behalf and the support team is going to contact you directly for the investigation of this technical issue.

aramyan.h

I have learned that the case is resolved with the following answer:

Advised to downgrade to httpx version 1.14.2 using the following commands.
-pip install httpx==1.14.2 (if you are an admin)
-pip install https==1.14.2 --user (otherwise)

Could you please accept if the issue is resolved, otherwise post another question if the issue still exists.