On the Unified Dashboards at UMP version 2.6.1 I am receiving this message on some of the pages: The multi-part identifier "nas.origin" could not be bound, I have deactive and active the wasp probe. Does anybody know how to solved it?
Can you check your alarm list and see if any of the alarms has a blank origin field?
I have reviewed and there is no blank field. I have attached the error message just in case.
Oh, you are getting the error in the list views. It may be related to QoS rather than alarms. Try checking your QoS objects and see if there is one with a blank origin.
Good question. That is a bit surprising because a hub with a blank origin setting in its config should set the origin on messages to the hub name. So I am not sure how you can pass messages over the bus that have an empty origin.
Is there anything in common between those QoS objects other than the fact that they have no origin? Do they come from the same probe, robot, or hub? Are they all new or old?
I have found that most of the list that have the problem are filled with QoS from probes that are in the same robot and taking a look on the perfomance reports designer i can see the robot repeted twice
See the attachtment.
You may be able to resolve the issue by manually setting an origin on those QoS objects in the Service Level Manager.
I am not sure why the QoS objects are missing the origin, and you can certainly dig into that further by manually generating new QoS objects from the robot with the nimqos command. This would tell you if it is an issue at the time the objects are created and if it is still ongoing. If you cannot reproduce the problem this way, you might have to wait for it to happen again to get more information.
Having two different QoS sources for the same robot is fairly common and mostly depends on which probes are generating the QoS. In some cases you can set an option or rename something to make the naming consistent. In other cases you might not be able to make them the same.
Retrieving data ...