Error on handshake port 9060 : TimeoutException

bjorn.carvalho

Hi, I'm facing an error while trying to use the Eikon API with Python: 021-01-25 09:50:58,021 P[2648] [MainThread 15368] Port 9060 was retrieved from .portInUse file 2021-01-25 09:50:58,022 P[2648] [MainThread 15368] Try to handshake on url http://127.0.0.1:9060/api/handshake... 2021-01-25 09:50:58,024 P[2648] [MainThread 15368] Request to http://127.0.0.1:9060/api/handshake headers = {'Content-Type': 'application/json', 'x-tr-applicationid': '52147867362a47a78287a31c5a9bd559e24e4ade'} params = None 2021-01-25 09:51:13,028 P[2648] [MainThread 15368] TimeoutException on HTTP request: ReadTimeout('') 2021-01-25 09:51:13,029 P[2648] [MainThread 15368] Error on handshake port 9060 : TimeoutException("TimeoutException on HTTP request: ReadTimeout('')")

bjorn.carvalho

Ok, just to give you give some follow up on my situation.

A Refinitiv support case was opened to investigate my issue further. Some changes actually needed to be performed on my profile, on Refinitiv side.

Now the API is working just fine. Thanks!

bjorn.carvalho

More details below:

jason.ramchandani01

@bjorn.carvalho Please see this thread to see if it can help. In particular please check httpx and nest-asyncio library versions and also then check with your IT Team that your firewall has permissioned the following:

(not sure which region you are in so I put all regions):

emea1.apps.cp.thomsonreuters.com 159.220.1.19
amers1.apps.cp.thomsonreuters.com 159.220.40.41
apac1.apps.cp.thomsonreuters.com 159.220.16.215

I have seen many issues where firewalls have been updated - so please do check that and confirm please. I hope this can help.

bjorn.carvalho

Thank you. I have checked my lib versions and here they are: httpx 0.14.3 nest-asyncio 1.3.3 I will try to reach my IT departement about firewall access to
emea1.apps.cp.thomsonreuters.com 159.220.1.19 as I believe this is the one for me, as I'm working from France.

bjorn.carvalho

Could you please explain me what happens in the Eikon Data Api log?

I'm not a developer, just what a Refinitv employee recently called a "citizen developer" but I would like to get a grasp on what is happening.

My understand is that Eikon Data API is connecting to my Eikon's local server on port 9060, to send an HTML GET on :

http://127.0.0.1:9060/api/handshake

which is timed out.

And now I assume, from what you've mentioned about firewall access to:

emea1.apps.cp.thomsonreuters.com 159.220.1.19
amers1.apps.cp.thomsonreuters.com 159.220.40.41
apac1.apps.cp.thomsonreuters.com 159.220.16.215

that the Refinitiv Eikon application is trying to connect to Refinitiv's emea server to perform that hanshake, which is timed out again.

Same thing happens when trying to use :

Request to http://127.0.0.1:9060/api/v1/data

I get this error:

HTTP Response: {"code":500,"message":"connect ETIMEDOUT 159.220.1.19:443","statusMessage":"Internal Server Error"}

Is that correct?

As @daichi.yuasa.b mentionned it in his thread related with the same issue, I tried a telnet on emea1.apps.cp.thomsonreuters.com:443 and this works just fine.

bjorn.carvalho

Here it is:

jason.ramchandani01

@bjorn.carvalho There could be many reasons for this happening - it may be best to open a support ticket for this but just before I do this - please could you try clearing the eikon cache and restarting the machine:

Launch Clear Cache from Windows menu >> Thomson Reuters >> Clear Cache

Please could you also update you eikon library to the latest 1.1.8 if you have not already done so:

pip install eikon==1.1.8

Try this and then rerun your code to see if it can return data.

a simple call will suffice:

df,err = ek.get_data('VOD.L',['TR.PriceClose'])
df

Try this and see if it helps. Otherwise I will open a ticket for you.

bjorn.carvalho

I did what you wrote but I still face the same issue.

jason.ramchandani01

@bjorn.carvalho Thanks for your patience. We need to continue investigating this issue with Refinitiv Support. I raised case 9568978 on your behalf with Refinitiv Helpdesk. You will be contacted by the Helpdesk.

jason.ramchandani01

@bjorn.carvalho thanks for coming back on this. Glad all is now working.