NT_ST_ROW errors seen in our protocols – how to diagnose further.

Solved388 views
4
0 Comments

Hello All,

We are seeing this error in our protocol and wondering of potential causes for this issue and what we can do to further diagnose the issue.

ManagedInterop|ERR|-1|16|NT_SET_ROW for 12200/4b8631fade8bf1f09700415e727adc7d failed. 0x80040221

Many thanks,

Ryan

ryan yahia Selected answer as best 18th April 2023

1 Answer

8
7.85K 0 Comments

Hi,

Error 0x80040221 means "Invalid data", that means that something is wrong in the objects that were passed to the call.

Best things to check to investigate this issue:

  • Open the protocol.xml of the element that is generating this issue and search for all protocol.SetRow calls
  • Check if the parameter id that is specified in the SetRow call is the parameter id of a table parameter (biggest chance that this is causing the error)
  • If all the parameter ids are valid then check if the rowKey that is being used is valid: does the row key exist and is the casing correct?
  • Last item to be checked is the row object that is being passed: is this an object[] array structure in the background?

What might help to locate the call that is causing the issue is to add a log line before and after executing the SetRow call in a temporary protocol.xml version, this way it helps to pinpoint the location where it's going wrong and then focus on the arguments that are being passed.

Regards,

ryan yahia Selected answer as best 18th April 2023