Eikon Api Data: Port number was not identified. Check if Eikon Desktop or Eikon API Proxy is running

yujin.xu11
yujin.xu11
in Eikon Data APIs

I went through many threads and no solution could fix the case.

Client upgraded Eikon DAPI library to the newest already.

Root cause was two ports(9000, 9060) were opened simultaneously and were in listening state after Eikon was launched. In this case, port 9060 was recorded in the file: AppData\Roaming\Thomson Reuters\Eikon API Proxy\.portInUse. Client changed the port to 9000 in portInUse file. However, it was rechanged back to 9060 after Eikon was restarted.

In my laptop, only port 9000 is opened after Eikon is started.

Why Eikon opened two ports in client side? Could anyone help to fix this issue?

Tagged:

Best Answer

Answers

  • Jirapongse
    Jirapongse admin

    @yujin.xu11

    On my machine, it opens two TCP ports:9000 and 9060.

    LocalAddress LocalPort  State OwningProcess
    ------------ ---------  ----- -------------
    127.0.0.1        62242 Listen         25188
    127.0.0.1         9060 Listen         20828
    127.0.0.1         9000 Listen         25572

    TCP port 9000 is for THOMSONREUTERS.EIKON.DESKTOPSXSSVC. I think it is for Side by Side API.

        25572 "C:\Program Files (x86)\Thomson Reuters\Eikon\Y\Bin\Eikonbox.exe" -n -a -eikonpid=25576                      
              -EikonProcessId=27136 -HwndComInterop=0x1 "-manifest=C:\Users\U8009686\AppData\Local\Thomson Reuters\Eikon   
              User\Cache\LibraryCache\9.0.53072_SL1-3ECHZ20__EikonContainer.dll.manifest"                                  
              "-Context=C:\Users\U8009686\AppData\Local\Thomson Reuters\Eikon                                              
              User\Cache\LibraryCache\Apps\THOMSONREUTERS.EIKON.DESKTOPSXSSVC\1.1.0.100" /prefetch:1    

    TCP port 9060 is for REFINITIVHOLDINGS.EIKON.DATAAPIPROXY. I think it is for Eikon Data API.

        20828 "C:\Program Files (x86)\Thomson Reuters\Eikon\Y\Bin\Eikonbox.exe" -ap -a -eikonpid=25576                     
              -EikonProcessId=27136 -HwndComInterop=0x1 "-manifest=C:\Users\U8009686\AppData\Local\Thomson Reuters\Eikon   
              User\Cache\LibraryCache\9.0.53072_SL1-3ECHZ20__EikonContainer.dll.manifest"                                  
              "-Context=C:\Users\U8009686\AppData\Local\Thomson Reuters\Eikon                                              
              User\Cache\LibraryCache\Apps\REFINITIVHOLDINGS.EIKON.DATAAPIPROXY\1.1.0.15" /prefetch:1

    Therefore, typically, 9060 is a TCP port for Eikon Data API.

  • chavalit-jintamalit
    chavalit-jintamalit admin

    Hi @yujin.xu11

    You can ask client to test these 2 URLs with a browser on the same machine

    http://localhost:9000/ping?all

    http://localhost:9000/api/status will be redirected to http://localhost:9060/api/status

  • yujin.xu11
    yujin.xu11

    Python still can't connect Eikon outside Eikon with the same error. Client can run Python code in codebook built-in Eikon.

    any further action to fix this issue?

    Output from client side:

    http://localhost:9000/ping?all

    ---------------------------------------

    {"port":9000,"mode":"eikon4","pid":7880,"hasSecure":true,"startedTime":"Mon Dec 21 2020 09:16:39 GMT+0800 (中国标准时间)","subApps":[{"path":"/heap"},{"path":"/ping"},{"path":"/sxs","data":{"hasSecure":true,"sxsApps":{}}},{"path":"/api"}]}


    http://localhost:9000/api/status

    ------------------------------------------------

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

  • andrej.oschlapow
    andrej.oschlapow

    How exactly did you solve the problem? I am struggling with the same issue.

Categories