EIKON API PROXY NOT RUNNING

Already checked that everything (Jupyter notebook, eikon) the latest version, Opened EIKON when running the code in notebook, eikon packege installed and running, just couldn't use ek.set_app_key('xxxxmy key here')

used a ps1 file found on this website to get the current results, no idea how to fix the problem

More details:

I've tried using this website for troubleshotting

https://developers.refinitiv.com/en/article-catalog/article/eikon-data-api-python-troubleshooting-refinitiv

I used what's in this, in step 4 it's SUPPOSED to be like

While my file looks like

Still not a clue

also I used eikon.get_port_number()

and it outputs 9060

don't know if that helps

Find more posts tagged with

python

eikon

workspace

eikon-data-api

refinitiv-dataplatform-eikon

workspace-data-api

Accepted answers

Hi,

To check if Eikon API Proxy is really running, open http://localhost:9000/api/status

If you have following response :

{"statusCode":"ST_PROXY_READY","version":"2.6.3"}

That means that python script failed for other reason (like this thread)

All comments

Hi,

To check if Eikon API Proxy is really running, open http://localhost:9000/api/status

If you have following response :

{"statusCode":"ST_PROXY_READY","version":"2.6.3"}

That means that python script failed for other reason (like this thread)

@pierre.faurel

Hi! Thanks. Right now I'm able to set key and I will just list what I did here in case anybody wants to know.

Just like what I mentioned in the question, the .portInUse file was not found. I manually created \AppData\Local\Thomson Reuters\Eikon API Proxy\.portInUse (a notepad text file) with 9000 as its content, but it's still not working.

I used this website again

https://developers.refinitiv.com/en/article-catalog/article/eikon-data-api-python-troubleshooting-refinitiv

and by looking at the s x s log file I found out that the actual port EIKON is using is port 9060.

After that I'm able to set key.

So I changed the text file from 9000 to 9060.

http://localhost:9060/api/status gives me the following output. While I still have no idea that means, I'm finally able to use set_app_key()...

{"statusCode":"ST_PROXY_READY","version":"2.6.0"}

Thank god it's resolved.

Quick Links