Application crashing with error 80131506

Dear team,
We are using RFA.NET 7 libraries in our WCF service. The WCF service is built on .NET framework v4.0.
We are experiencing the below mentioned error when we are trying to connect to Reuters from the WCF service
Error:
Application:
DataService.Server.WCF.Service.exe
Framework Version: v4.0.30319
Description: The process was
terminated due to an internal error in the .NET Runtime at IP 000007FEF9131A48
(000007FEF9060000) with exit code 80131506
When we checked the problem on MSDN sites, we came to know that it is because of concurrent garbage collection and we have disabled it by setting <gcConcurrent enabled=false/> in the app.config file. Even then, we are facing this error.
Upon investigation, came to know that the exception purely occurs when an unmanaged code is not properly disposing the objects via the GC
Investigation point:
the problem was a C++/CLI library in which there was a call to the NtQuerySystemInformation; for some kind of reason sometimes (and under mysterious circumstances), when it was called the CLR heap got corrupted and the application crashed.
So, we assume that the RFA.NET 7 library is built on C++ and could you please investigate on the occurance of this error from your end
Best Answer
-
Hello @sri-satya-kri.challa,
I can not overstate the importance of your organization being on a currently supported version of RFA.NET. The quickest way to verify this is to consult with
RFA .NET 7.5 was End-Of-Life 12/31/2016. The currently supported version is RFA.NET 8.0
So in order to be on a supported version the app will need to migrate to RFA .NET 8.0.
---
In terms of effort versus reward, if I was contemplating an API migration off an unsupported version, in order to be on a supported API, I would heavily consider migrating Elektron API Suite - and Elektron Websocket API.
Elektron is our current, most efficient API suite, for a while new features have been coming out in Elektron APIs, and new features will continue to be made available in Elektron APIs.
RFA is fully supported (the versions are listed in the above link), if the migration effort is required, it's feature-complete API versus the latest, continuously improving and evolving API.
This was the consideration, if your application is existent and started experiencing the issue that you describe. For a newly developed application Elektron API suite is the API of choice.
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
- 684 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
- 249 ETA
- 554 WebSocket API
- 37 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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 中文论坛