In the Infrastructure Manager
, try doing a SHIFT-double-click on the probe. This forces the Infrastructure Manager
to re-fetch the GUI tool from scratch, regardless of whether there is a copy on the local workstation or not. You should very briefly see a "fetching user interface for <probe_name>..." message box.
There can be security issues with this action as the software tries to write to read-only files in these folders where the conf files sit.
To resolve this issue, change permissions if necessary to allow writes into the directory that contains the configuration GUI's. (Full access)
If that doesn't work you can copy the conf_<probe>.exe into the directory it's complaining about and try again.
C:\Users\Nusername>~1.HAS\AppData\Local\Temp/util/conf_<probe_name>.exe for write.Also check, does logging in as a Windows Administrator and opening the probes exhibit no issues at all?
Is the workstation with the problem on a different network? (There may be a session ID problem -- we hash the IP address of the workstation and that might be different from the point of view of the login hub vs. the distribution server).
Check that the package name for the probe has not been changed. This can been checked using the Infrastructure Manager
. Click on the robot so that the list of probes is in the upper right window. Scroll the list to the right until the package name
column appears. Make certain the name in this column is the same as the name of the probe.
Also, check the distsrv probe log on the login hub. At log level 1 or 2 you should see the get_configuration
command asking for the probe configuration tool.
Check the registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Nimbus Software\NimBUS Installation
or \HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\Nimbus Software AS\NimBUS as shown here for 'Home':
When you login to the Infrastructure Manager make sure you have selected the correct IP address in the bottom of the window (Hub IP).
Make sure that the probe package .zip is physically on the box and seen by the distsrv.
Ensure that you have the correct hub address selected in Tools->Options in the Infrastructure Manager.