@vanderkroon

It looks like Eikon API Proxy app does not behave as expected on your Mac. The timeouts and the crashes you experienced are not the normal behavior. This is why @Gurpreet. suggested you contact Refinitiv Helpdesk to investigate the root cause of the timeouts and the crashes. This said, if you're looking to launch Eikon API Proxy from Python script on a Mac, you can use the following code.

import subprocess
subprocess.run(['open', '-a', 'Eikon API Proxy.app'])

Since Eikon API Proxy does not signal to the operating system when it finished launching and establishing connection to Eikon platform (in other words when it's ready to be used), you will need to wait an arbitrary period of time after launching Eikon API Proxy before you start executing data requests using Eikon Data APIs.

Hi @vanderkroon,

The API proxy automatically starts when the Eikon is running on the desktop; you don't have to start it in your python code. Just use:

import eikon as ek
ek.set_app_key('--YOUR APP KEY--')

The second statement will initialize the library's connection to already running proxy.

I understand that your statement will initiate access to the ThomsonReuters database and I have used it ever since my subscription started.

Unfortunately I run into a situation where the TR server no longer responds in the middle of a script that retrieves data. I will then get getting some type of time-out error which occurs too often, e.g. even this morning. The message that the Eikon API proxy returns is:

Error code: 100

Error message: Unhandled Rejection at: Promise [object Promise] reason: Error: net::ERR_TIMED_OUT

So I want to catch this situation with the <<try>> - <<except>> facility where I want to reconnect by first killing the Proxy and the restart the proxy followed by a re-initiate statement as per your answer.

So back to my original question: how to I get the Eikon API Proxy to run after it produces a "Error code 100" ?

Any suggestions are still quite welcome.

FYI: Another error message that the Eikon API Proxy occasionally produces is:

An unexpected error has occured.

Eikon API Proxy needs to be restarted.

We are sorry for the inconvenience.

TypeError: Cannot read property 'toString' of undefined

at fs.readFile (/Applications/Eikon API Proxy.app/Contents/Resources/app.asar/node_modules/eikon-module-settings/src/settingssoap.js:67:29)

at ELECTRON_ASAR.js:122:7

at _combinedTickCallback (internal/process/next_tick.js:73:7)

at process._tickCallback (internal/process/next_tick.js:104:9)

I don't restarting the proxy is the right way to approach this problem. I would recommend that you open a service ticket with Refinitiv to look into your Eikon/proxy.