We get the following error message from the server: "NakCode:AccessDenied" "Text:902: Cannot Create

We get the following error message from the server:

"ID:1"
"Type:Ack"
"AckID:0"
"NakCode:AccessDenied"
"Text:902: Cannot Create a Record"
"Key:Service:DEX_CTB_PRD"
"Name:ATS_RM_CREATE"


The message says our access is denied but it would be very strange if we were allowed to create a RIC with "ATS_INSERT_S" delete any RIC with "ATS_DELETE_ALL" but not to create a RIC with "ATS_RM_CREATE". It seems to us the JSON is probably incorrect.

Our biggest problem is that we don’t have any documentation describing the different instructions such as ATS_DELETE_ALL / ATS_INSERT_S / ATS_RM_CREATE and the fields such as X_RIC_NAME / X_BU / X_CONTAINER / X_PE / X_MODEL…

1) Would you by chance have some documentation or dictionary describing those?

2) Is ATS_RM_CREATE still supported by WebSocket?


3) Do you see any mistake in our JSON: {"ID": 1, "Type": "Post", "Key": {"Service": "DEX_CTB_PRD", "Name": "ATS_RM_CREATE"}, "Ack": true, "PostID": 0, "Message": {"ID": 0, "Type": "Refresh", "Fields": {"X_RIC_NAME": "TESTABREG=BELB", "X_BU": "ATS", "X_CONTAINER": "DEFAULT", "X_PE": "0", "X_MODEL": "DERIV05", "X_LINK": "1", "X_PPE": "0"}}}

Best Answer

  • wasin.w
    wasin.w admin
    Answer ✓

    Hello @LanceGabriel.Villacrusis

    I checked the ATS Operation document (Refinitiv_ Real-Time Advanced_ Transformation_ Server_Operations.pdf file in the ATS server package). It describes the ATS_INSERT_S and ATS_RM_CREATE commands as follows:

    • ATS_INSERT_S: create records from Contribution Commands via the Enterprise Platform or sink application.
    • ATS_RM_CREATE: create records from ATS models via the Enterprise Platform or a sink application. A model must exist before you can create a record from model.

    The document also contains the negative FID information too.

    table.png

    According to the WebSocket API - contribution point of view, the client's JSON post message is a valid JSON message format.

    Since the error is generated from the ATS server, I strongly suggest you contact the ATS Support team to verify the client's ATS setting and permission. You can contact the ATS Support team via https://my.refinitiv.com/content/mytr/en/helpandsupport.html website.


    contact-ats-support.png

Answers

  • Hi @wasin.w so to confim

    1) Would you by chance have some documentation or dictionary describing those?

    Answer: everything is in the ATS Operation document (Refinitiv_ Real-Time Advanced_ Transformation_ Server_Operations.pdf

    2) Is ATS_RM_CREATE still supported by WebSocket?
    Answer: Yes
    3) Do you see any mistake in our JSON: {"ID": 1, "Type": "Post", "Key": {"Service": "DEX_CTB_PRD", "Name": "ATS_RM_CREATE"}, "Ack": true, "PostID": 0, "Message": {"ID": 0, "Type": "Refresh", "Fields": {"X_RIC_NAME": "TESTABREG=BELB", "X_BU": "ATS", "X_CONTAINER": "DEFAULT", "X_PE": "0", "X_MODEL": "DERIV05", "X_LINK": "1", "X_PPE": "0"}}}

    Answer:JSON post message is a valid JSON message format.


    With regards to the error message we would need to reach out to ATS team correct? this is not an issue with the use of ATS_RM_CREATE ?

  • Hello @LanceGabriel.Villacrusis

    The client's JSON post message is a valid JSON message for the WebSocket API, but it needs to be checked with the ATS team to verify if the attributes and values match the ATS requirement.

    Question: With regards to the error message we would need to reach out to ATS team correct? this is not an issue with the use of ATS_RM_CREATE ?

    Answer: Yes.

    The "NakCode:AccessDenied - Text:902: Cannot Create a Record" is generated from the ATS server, so I suggest you reach out to the ATS team to verify why the client has an issue with ATS_RM_CREATE command while the ATS_INSTERT_S work fines.