Error code 503 | Server Error: API Proxy is not available

eikon.eikonError.EikonError: Error code 503 | Server Error: API Proxy is not available

Started to get this errors recently. Cleaning Eikon cache helped to fix the first occurrence of this error few days ago, but now the error is back and cleaning cache no longer helps. Rebooting PC is the option I'd try to avoid.

http://localhost:9000/ping?all

{"port":9000,"mode":"eikon4","pid":107696,"hasSecure":true,"startedTime":"Wed Jul 15 2020 15:34:51 GMT+0300 (Russia TZ 2 Standard Time)","subApps":[{"path":"/heap"},{"path":"/ping"},{"path":"/sxs","data":{"hasSecure":true,"sxsApps":{}}},{"path":"/api"}]}

http://localhost:9000/api/handshake

API Proxy is not available

Find more posts tagged with

python

eikon

workspace

eikon-data-api

refinitiv-dataplatform-eikon

workspace-data-api

Accepted answers

jason.ramchandani01

Hi @ivan.cherkasov our dev team have investigated this issue using the versions you gave and have the following advice:

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.

All comments

jason.ramchandani01

Hi @ivan.cherkasov thanks for your question - the Eikon API Proxy may not be running on the machine. Though it appears frm your pingall trace it is running. I have experienced this following occasions when there is a dropped connection and reconnect.

Please follow steps in this article to verify if the Eikon API Proxy is running.

I hope this can help.

ivan.cherkasov

I cleaned cache, rebooted, cleaned cache, started Eikon. It seems that the proxy managed to start after that. Though now it jumped to the port 9100

http://localhost:9100/api/handshake

{"code":404,"message":"Not Found","statusMessage":"Not Found"}

even if I type 9000 port in the URL above. Wonder how long it would last.

Is there any way to restart Eikon without rebooting? Some sort of a service to be restarted or smth. like that?

Hi,

What is the response when you type http://localhost:9000/api/ in a browser ?

You should have this :

ivan.cherkasov

Wow, never saw smth. like this.

Now (when proxy started, supposedly, since the 503 error is gone).

http://localhost:9000/api/ redirects my browser to http://localhost:9100/api/ which shows the following string, whatever that means:

{"code":500,"message":"Cannot find module \".\"","statusMessage":"Internal Server Error"}

That could mean that you don't have an Eikon variant available for Data API Proxy (despite that Eikon Proxy is running on the machine).

Could you detail Eikon and eikon lib versions ?

ivan.cherkasov

That's odd, because I was using Eikon API proxy for past several years (from python) with this terminal. Versions are the following:

Desktop 4.0.52 (4.0.52055)

PROXY (9.52.0.51)

>>> eikon.__version__

'1.1.2'

nick.zincone

Hi @ivan.cherkasov,

Given you are using Eikon 4, you will need to use the command: http://localhost:9000/ping?all which you have been doing. Secondly, you can't simply use the handshake as a GET:http://localhost:9000/api/handshake. The handshake request needs to be sent as a POST message with a body.

jason.ramchandani01

Hi @ivan.cherkasov our dev team have investigated this issue using the versions you gave and have the following advice:

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.

ivan.cherkasov

I'm sitting behind the corporate firewall and it appears that sometimes smth. is blocking Eikon updates or components installation (if cache was cleared, for example) or maybe smth. else it requires, resulting in odd errors like in the subject of this thread. Our IT teams investigates these on case-by-case basis, and so far Eikon is working for me.

However it is quite hard to figure out what exactly is going on when such thing happens. For example, right now I'm successfully fetching data via python api and, supposedly, proxy is running, but for http://localhost:9000/api/ in the browser I see the following:

{"code":500,"message":"Cannot find module \".\"","statusMessage":"Internal Server Error"}

For http://localhost:9000/ping?all I see

{"port":9000,"mode":"eikon4","pid":74148,"hasSecure":true,"startedTime":"Fri Jul 31 2020 08:00:05 GMT+0300 (Russia TZ 2 Standard Time)","subApps":[{"path":"/heap"},{"path":"/ping"},{"path":"/sxs","data":{"hasSecure":true,"sxsApps":{}}},{"path":"/api"},{"path":"/sxs/v1/services/messenger"},{"path":"/sxs/v1/services/messenger"},{"path":"/sxs/v1/services/messenger"},{"path":"/sxs/v1/services/messenger"},{"path":"/sxs/v1/services/messenger"}]}

Jirapongse

I got the same error as yours when using the browser to get http://localhost:9000/api/. I was redirected to port 9060.

However, my Eikon Data API works fine.

EXPLORE OUR SITES