Hi,
I noticed that the error appeared again, but observing the repetition of the event I understood that when NetXMS adds a new node through network discovery, this node would later generate the error in the database.
I'm not sure what the reason is, but it seems to me that if the node is not compatible with the agent, simply check the option to disable the use of the NetXMS agent in the status poll and the error would disappear.
It seems to be some bug.
I noticed that the error appeared again, but observing the repetition of the event I understood that when NetXMS adds a new node through network discovery, this node would later generate the error in the database.
I'm not sure what the reason is, but it seems to me that if the node is not compatible with the agent, simply check the option to disable the use of the NetXMS agent in the status poll and the error would disappear.
It seems to be some bug.