Config file robot.cfg lost most content

[steven spray]

Hi all

I've seen two past posts on this issue and although there were a lot of feedback on the possible causes, I am yet to see a resolution, so starting this new thread.

Just like the older posts, I received an alarm that a robot is inactive. After troubleshooting, I saw the robot.cfg file only contained the following information...

<controller>
   reuse_async_session = 1
</controller>

Now, I'm not that interested to find out why this might have happened, be it AV or some other 3rd party tool interfering with this file. I just want to resolve this issue. One fix is to just reonboard this server from scratch. However, all UIM config will be lost and this server has like 30 custom database instances, so this is not really a viable option. The other option I was thinking of would be to merely rebuild this robot.cfg file. I have a sample that I can just copy+paste and then readjust for the server. However, I'm not sure if this will work, or cause more problems.

Does anyone else have any other ideas or know if what I'm thinking will work?

Thanks for reading
Steven

[Garin Walsh]

Robot writes its config file on shutdown and doesn't handle errors - so fill install drive and you restart the robot and you lose the config. Been over a decade waiting for a fix to this.

If you have the controller set to save configs, check C:\Program Files (x86)\Nimsoft\robot\cfgs to see if you have a saved config.

[steven spray]

Hey Garin

Thanks a bunch for the reply, appreciated!

[Jim Christensen]

Hi,Using your sample file or a file from a peer robot and editing the server specific entries ( like robotname,robotic, etc...) will work.Sent from my T-Mobile 5G Device