Tick History Rest API: Error in curl::curl_fetch_memory(url, handle = handle) : schannel: next Initi
However since the past few days I have started getting the below error while establishing connection
url <- "https://selectapi.datascope.refinitiv.com/RestApi/v1/Authentication/RequestToken"
b <- list(Credentials=list(Username=jsonlite::unbox(uname),Password=jsonlite::unbox(pword)))
r <- httr::POST(url,add_headers(prefer = "respond-async"),content_type_json(),body = b,encode = "json")
Error:.....
Error in curl::curl_fetch_memory(url, handle = handle) :
schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed).
Best Answer
-
Hi @Jirapongse
Client was able to resolve the issue at their end.The issue seems to be with the underlying curl.exe file. The actual solution is present in this stackoverflow thread.
1
Answers
-
Hello @Vinod A ,
I am assuming that your credential remains valid, and you are able to login to DSS GUI portal successfully.
I would try to determine if the access issue is limited to curl request. By testing with RTH Postman Starter -> User authentication request or RTH Python Code Samples to see if the authentication request goes through this could be confirmed.
Let us know how this works on your side, and if you are able to narrow down the issue specifically to curl requests
0 -
Hi @zoya faberov Thank you. I do not see any issues on my side. This has been raised by client.
Client is using R libraries to extract tick history data . And have been using the same code base for over and year and has been working up until now. Nothing has changed on their side and would want to know reason why it’s not working anymore.
However since the past few days they have started getting the below error while establishing connection
url <- "https://selectapi.datascope.refinitiv.com/RestApi/v1/Authentication/RequestToken"
b <- list(Credentials=list(Username=jsonlite::unbox(uname),Password=jsonlite::unbox(pword)))
r <- httr::POST(url,add_headers(prefer = "respond-async"),content_type_json(),body = b,encode = "json")
Error:.....
Error in curl::curl_fetch_memory(url, handle = handle) :
schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed).
0 -
Sorry about the issue that you are facing.
I can run the code properly. Internally, httr uses libcurl to send HTTP requests. According to the error message, the libcurl is unable to establish the connection to the DSS server with schannel. You may need to enable a verbose log to see more information.
r <- httr::POST(url,add_headers(prefer = "respond-async"),content_type_json(),body = b,encode = "json", config=config(verbose=1))
Then, you will see the following log on the console.
I hope that this information is of help.
0 -
Hi @Jirapongse - Thank you for your help.
Client is still getting the same errors.
Can you paste the output of sessionInfo() from your Rsession. I can try and compare what version of curl and httr packages you have.0 -
Please see below.
0 -
Hi @Jirapongse, Unfortunately, this did not help client.
Is there any firewall issues that could impact this ?
Or any recent update in norton anti virus you are aware of that could prevent the ssl connection to be established?
0 -
I assumed that the client uses Windows. According to this page, curl is available on Windows 10/11.
You can run the following command in the command prompt or PowerShell to verify the curl version.
curl.exe -V
It should use Schannel.
Then, run the following command to test the connection.
curl.exe -iv -H "Content-Type: application/json" -H "Prefer: respond-async" -X POST -d "{\"Credentials\": {\"Username\": \"username\",\"Password\": \"password\"}}" https://selectapi.datascope.refinitiv.com/RestApi/v1/Authentication/RequestToken
If the problem also happens with this curl command, it could relate to settings on the machine.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛