Controller The next admin check time is too far into the future
Updated On:14-02-2018 07:39
CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)NIMSOFT PROBES
QOS data stopped inserting into database only for this particular server.?We had checked all our hub's queue. The QOS data reaches our primary hub, but it's unable to insert into our database.
See the below information in the robot controller logs showing wrong date/timestamps
Jan 3 00:08:53:171  Controller: The next admin check time is too far into the future (4924933 seconds). Jan 3 00:08:53:171  Controller: This indicates that the clock has been changed and a robot restart is needed.
The?log ?indicates?that the clock or clock synchronization is broken on the server where the robot is installed.
Stop the robot, then correct the clock on the server and then start the robot.