I am unable to successfully ping the Eikon Side by Side server, even though I can see the process...

... running. What is the process to troubleshoot this error?

I am unable to successfully ping the Eikon Side by Side server, even though I can see the process running. What is the process to troubleshoot this error?

WIth Eikon Desktop running, using Process Explorer, I can see 3 processes with 'DesktopSxS' as part of the process name. All 3 processes are EikonBox.exe processes. This seems to confirm that Side by Side is running.

However, when I send a 'get' to 'http://127.0.01:9000/ping', I don't get any response.

How can this error by troubleshooted?

Find more posts tagged with

side-by-side-api

Accepted answers

peter.vonbredow

Thanks Alex.

It turned out that the root of the problem was that Postman's default proxy settings were stopping this from working. I tried:

'http://127.0.01:9000/ping

in a browser, and it worked, although it had failed in Postman. Once I switched off the proxy settings in Postman, everything worked correctly.

All comments

Alex Putkov.1

You have a dot missing in the loopback IP address. Some applications, e.g. Safari may interpret your notation as loopback IP address, but not all applications will. Correct the loopback IP address or consider replacing it with "localhost" alias. If the missing dot was just a typo when posting on the forum and in your test you used correct address, in other words if incorrect loopback IP address is not the issue here, check out the following article on troubleshooting issues with Eikon Data API.
https://developers.refinitiv.com/article/eikon-data-apipython-troubleshooting-refinitiv

Also see the following discussion.
https://community.developers.refinitiv.com/questions/49611/port-number-was-not-identified-check-if-eikon-desk.html

peter.vonbredow

Thanks Alex.

It turned out that the root of the problem was that Postman's default proxy settings were stopping this from working. I tried:

'http://127.0.01:9000/ping

in a browser, and it worked, although it had failed in Postman. Once I switched off the proxy settings in Postman, everything worked correctly.

EXPLORE OUR SITES