Contribution DeniedBySource: Marketfeed Format error
Hello!
We get the following Ack message during attempt to contribute data for test instrument:
AckMsg
streamId="1"
domain="MarketPrice Domain"
ackId="1"
nackCode="DeniedBySource"
text="Marketfeed Format error"
name="<instrument>"
nameType="1"
serviceId="291"
AckMsgEnd
What is the reason for this response? Could it be some misconfiguration for contribution service?
Thanks!
Best Answer
-
Thanks for the reply. Unfortunately, there is not enough information to diagnose what may be going wrong. It could well be a contribution server issue - but I cannot say based on what you have provided.
You can ask your client to enable the XmlTrace option in their config - for EMA C++ you can enable XmlTraceToFile and set the other related parameters to generate the tracefile.
For EMA Java they can enable XmlTraceToStdout and redirect to a file.
They can then raise a support ticket and share the trace file to help the support team understand what may be going wrong.This forum is best suited for programming how to advise and simpler diagnostics.
0
Answers
-
The text of the AckMsg indicates a Formatting error.
Can you confirm which API you are using and provide an example of what you are contributing?
One test would be to perform a very simple post - e.g. with a single String field in the payload. This would help determine it their is indeed a formatting error in your fuller payload or perhaps an issue with the contribution server configuration.
0 -
Hello @Umer Nalla
Thanks for answer!
We are using EMA API (PostMsg). FIDs for contribution: "DSPLY_NAME (3)", "GEN_VAL2 (997)". Service: "DCSIP (291)".
0 -
Did you try just contributing DSPLY_NAME with a string as I suggested? Do you still get a Nack - if so it would suggest that you are not encoding GEN_VAL2 correctly.
When I asked for an example of what you are contributing, I meant a code snippet - so we can see if you are encoding the fields correctly.
0 -
Hello @Umer Nalla
Actually, our application (based on EMA API) is used in two places. On our side it works correct for the same FIDs and MARKETLINK service (id: 266). But problem is observed on customer's side during the contribution.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛