UIM - Probes Error Validation Status - all probes in red status
search cancel

UIM - Probes Error Validation Status - all probes in red status


Article ID: 34314


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)


All probes turned red.


  • Any UIM release


Was there a recent IP address change on this host/relay?

In any case, when you see Error validation in the 'Active' column in the Infrastructure Manager, you just have to select the probes and right-click and select Security->Validate then Yes to all.

Allows you to validate (manually start) the selected Probe if the Robot Controller is not able to start it. The probe icon will appear red with a lock symbol on the rt-side bottom corner in the Probes list in the Main Window, and status shown in the Active column will be Error Validation.

In the Package Editor, used when designing Probe packages, a Check CRC flag can be set. The checksum is written to the controller.cfg file at Probe distribution, and will be compared each time the Probe is started. If the controller detects that the checksum has changed, it refuses to start the Probe.
You may then either re-distribute the Probe, or (if you know that nothing seriously is wrong) select Validate to start the Probe.

Security->Validate resets the security token on the probes, this issue is usually seen following a IP address change or a hardware change.

When a probe is distributed to a robot, the controller creates a magic_key which is a combination of the probe name, robotname, and the checksum of the probe's binary (stored in the controller.cfg). When the robot starts up, the controller will validate this magic_key for the probes that shall be started.

If the validation fails, the controller will not start the probe.