IEikonDesktopDataAPI initialize warnings
SD_BOOTSTRAP: Configuring traces from resource IDR_XML_TRACE_SOURCES Log config warning: TraceSource 'SD_BOOTSTRAP' already exists and will be reconfigured
Log config warning: TraceSource 'BOOT_SCHED' already exists and will be reconfigured
Log config warning: TraceSource 'SD_FDM_MISC' already exists and will be reconfigured
Log config warning: TraceSource 'SD_FDM_ASYNCDF' already exists and will be reconfigured
Log config warning: TraceSource 'SD_FDM_WKTH' already exists and will be reconfigured
SD_BOOTSTRAP: Configuring traces from file C:\Users\igorg\AppData\Local\Thomson Reuters\Eikon\X\Config\Traces.xml
Every time I run IEikonDesktopDataAPI->Initialize(&status). it send me the warnings above to the console. Is there a way to hide them?
Best Answer
-
@igorgI'm pretty sure this output to the console is unintentional, and I don't believe there's any way to suppress it. Out of curiosity, why do you care?
0
Answers
-
@igorg unfortunately there is no way for me to check, but I think it would be regulated by the logging settings for the terminal. Try going to Thomson Reuters > Configuration Manager > Logs and reduce the logging levels. It is either that or that you are running your app in the 'debug' mode.
0 -
I know I marked this answer as accepted. However, Configuration manager log settings didn't help.
For second reason, what exactly do you mean by 'running app in Debug mode'?
0 -
We have a tool that runs different applications and monitor the return codes, standard output and standard error output... Those warnings go to cerr and it makes our tool to think something went wrong and generate different kind of alerts.
0 -
I see. Well I'm afraid I don't see what can be done about it short of modifying your tool to ignore these warnings, if that's even a possibility. These warnings shouldn't be output to the console to begin with, however Eikon COM APIs libraries are in care & maintenance and there's no chance they will see any enhancements. Only most critical bugs can be considered. Since this issue hardly qualifies as a critical bug, I'd say there's no chance it will be fixed.
0 -
Understood. 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
- 688 Datastream
- 1.4K DSS
- 624 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
- 255 ETA
- 557 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
- 276 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
- 692 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
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 10 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛