Eikon 4.0.52 upgrade. RSearchMgr - cannot initialize
This is my forth problem after Eikon was upgraded to 4.0.52.
The program creates all necessary object and connects to EIkon. After it receives the feedback with EikonDesktopDataAPILib::Connected, it starts to create RSearch objects:
l_hr = m_EikonDesktopDataAPI->CreateRSearchMgr((IUnknown **)&m_RSearchMgr);
if (l_hr == S_OK)
{
// Initialize the RSearch manager and retrieve a session cookie
CComVariant l_EmptyVar;
l_EmptyVar.vt = VT_ERROR;
l_EmptyVar.scode = DISP_E_PARAMNOTFOUND;
l_hr = m_RSearchMgr->Initialize(RSearchLib::RS_CT_EIKON, l_EmptyVar, &m_RSearchMgrCookie);
if (l_hr != S_OK)
{
string error("[DCProviderEikon] Couldn't initialize RSearchMgr");
logger->Log(error, DCLogger::DC_LOG_LEVEL_ERROR);
DataCollectorHelper::CoutLog(error, DC_RED);
// Release the RSearch manager
ReleaseRSearchMgr();
}
}
It fails on Initialize step.
I'm 90% sure that it happens after the following steps/events:
1. EIkon started on the machine1
2. In several hours someone logs to Eikon in with the same user/pwd on machine2
3. There is a notification about the event #2 on Windows Desktop - as expected
4. Our program starts
5. Eikon asks (or does not ask , if the user was logged out on machine2) to sign in. User Signs In
6. Program receives 'Connected' event and start RSearchMgr initialization. And it fails.
Is this known issue ? If not, what can cause this behavior? It started this week, after Eikon upgraded itself.
Thanks.
P.S. The problem usually can be solved by shutting down Eikon completely and then start again.
Best Answer
-
Sorry for late response. Are you able to consistently reproduce the issue as you described it? I just tried reproducing it on my end using the C# example in RSearch tutorial and following the replication procedure you outlined, and I didn't experience any problems.
0
Answers
-
Ok, I'm getting the same problem (now with 4.0.61).
This line returns something but not S_OK:
l_hr = m_RSearchMgr->Initialize(RSearchLib::RS_CT_EIKON, l_EmptyVar, &m_RSearchMgrCookie);
if (l_hr != S_OK)
{How can I check the reason for the failed Initialize call?
Thanks
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 616 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛