The file size of robot.cfg is zero
This happens if the server was unexpectedly shutdown i.e. not a normal clean shutdown. We have also seen this problem where the /opt filesystem becomes full and the robot cfg is unable to be written out.
A rarer occurrence involved the anti virus program interfering with the nimsoft processing
1) Stop the robot
2) Copy the robot.cfg file from a working robot machine and paste in to the problematic robot machine and check the Robot name and ip address in the robot.cfg file and save it
3)Restart the robot