Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
avatar image
Question by yajnasteju · Feb 14, 2017 at 12:46 AM · elektronema c++configurationemaconfig.xmllog

Specifying EmaConfig.xml when running EMA Consumer application using start-stop-deamon

There are two issues that I am facing :

1 . Though the EmaConfig.xml in the directory specifies log type as stdout , the application prompts that file could not be opened .

Exception Type='OmmInaccessibleLogFileException', Text='Failed to open emaLog_13892.log file for writing log messages.'

2 . In case the log type is file , what is the location in which the file will be created , or can we specify the file log path

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by moragodkrit.chumsri_1 · Feb 14, 2017 at 04:19 AM

@yajnasteju

#1 what you mean is your application print the Logger message to console and it also try to open a new file to write a logger messages at the same time? If there are some typo in LoggerType such as using LoggerType::Stout instead of LoggerType::Stdout, it looks like EMA will write logger messages to the file by default. And if the application does not have permission to write file in running directory it will throw the exception. Not sure if this is the case or not.

#2 if your application installed as daemon for example, using windows services. It will run from a different context than normal user-mode applications, it's best if you don't make any assumptions about working directories or relative paths and the permission. As far as I understand default running directory for the service should be system folder such as c:\windows\system32. Using an absolute path to the file that your service needs should avoid this problem entirely.

For EMA, I can't find configuration to specify log location/folder but you can set absolute path to Log file name as below

<LoggerType value="LoggerType::File"/> 
<FileName value="c:\myapp\Logs\emaLog"/> 

Don't forget to create folder "c:\myapp\Logs" before start the service or daemon.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
9 People are following this question.

Related Questions

Electron RFA.NET API vs EMA API

Recommendation on API selection

Please make Elektron MRN Tutorial sample code VS140 compatible

How to get news headlines and content for an RIC

Getting NPE during consumer initialization for Elektron

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges