On IM shows Primary Hub in Red state but the process and nimbus service is up and running
No new logs being generated by controller or hub
Release : 20.4
We was not able to rename the nimsoft folder after stop the nimbus folder to restore the old backup so something was wrong like 3rd party tool scanning ( Anti Virus) or OS issues to stop the process.
We saw no errors in the logs/event viewer but either no new logs being generated.
So we see that via Regedit/Nimbus Service actually was starting the nimsoft via default path:
"C:\Program Files\Nimsoft\bin\nimbus.exe"
But the correct path based on your the customer installation is:
"F:\Program Files(x86)\Nimsoft\bin\nimbus.exe"
After we set the correct one and manually started the service via nimbus.exe or nimboss.exe it worked!
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NimbusWatcherService.
In the key "ImagePath" change the value to path (using the same case) as it appears in Windows Explorer. (for e.g. "C:\Program Files\Nimsoft\bin\nimbus.exe"). **
Restart the "Nimsoft Robot Watcher" service
**: ensure the paths are exactly the same, maintaining upper or lower case as even an upper case vs lower case can cause this issue.