RFA C++ 8.2.2 Win: Session request through Excel COM Add-in failing

I am trying to migrate our Excel COM add-in x86 build using RFA 7 to x64 using RFA 8.2.2. New COM component works during Unit Test (while making call directly), but when we run via Excel, it fails to send out connection request. No request going out on the wire either.
All I see in the log is:
[Tue Oct 8 11:43:30 2024]: (ComponentName) Connections: (Severity) Error: Failed to load the library "Connection_RSSL", the system error message is "The specified module could not be found.
Error Code: 126 Mode File: RFA8_RSSL_Cons_Adapter"
[Tue Oct 8 11:43:30 2024]: (ComponentName) Connections: (Severity) Error: Failed to create connection : "Error acquiring Connection (acquire returns null) - Connection_RSSL".
Best Answer
-
Thank you for reaching out to us.
I got the same error message if I deletes the RFA8_RSSL_Cons_Adapter143_x64.dll file from the working directly. Therefore, the RFA API can't find this file.
[Wed Oct 9 10:31:33 2024]: (ComponentName) Connections: (Severity) Error: Failed to load the library "Connection_RSSL", the system error message is "The specified module could not be found.
Error Code: 126 Mode File: RFA8_RSSL_Cons_Adapter"
[Wed Oct 9 10:31:33 2024]: (ComponentName) Connections: (Severity) Error: Failed to create connection : "Error acquiring Connection (acquire returns null) - Connection_RSSL"You need to check the working directory used by Excel COM Add-ins and make sure that the RFA DLL files are in that directory. Otherwise, you may copy the RFA DLL files to the c:\windows\system32 directory.
0
Answers
-
Many thanks @Jirapongse for getting back. I already have all the dlls in the directory. I tried to compare my add-in connection request with the unit test and this is what I found and might help to identify what could be the issue here:
One of the thread try to acquire connection making calls to
sessionLayer::acquireSASS3_Connection in Unit Test and sessionLayer::acquireRSSL_Connection in Excel Add-in.
My configurations are in registry and expect both to use it. If they are, why is this different and what configuration should I check. Also why acquireSASS3_Connection load RSSL_cons _* dlls, but acquireRSSL_Connection fails to load?
0 -
@Jirapongse, on back of your suggestion I tried adding RFA directory to path and it worked. Many thanks for your help. Looks like as it is operating through Excel, indirectly loading dlls need to be on path. This wasn't the case with x86 working with Excel 2016.
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
- 615 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 中文论坛