Trying to deploy dirscan v3.18 to a number of systems and dependency not found error is thrown.
- probe dependencies
You will find that the following OSes are NOT supported:
You may also open the probe package version in the local archive and click the dependencies Tab to see what dependencies are listed for a given OS, e.g.,
Windows x64 systems:
If the cause of the error is not clearly displayed in the deployment window, when the probe loglevel is set to 5 and logsize set to 100000, you can normally determine the underlying cause of the dependency not found error by running the deployment with the log open so you can watch it and see why its failing.
In some other cases, when the environment is configured to use 'Use remote distsrv on distribution' and the downstream distsrv is not using its local archive (meaning it will pull the package from the upstream distsrv) the downstream distsrv will check and validate that the upstream distsrv has ALL dependencies from ALL probe package Tabs present. If the remote distsrv is being used (instead of the local hub archive), and the package is present in the remote distsrv archive on the remote hub, with all probe package dependencies met/present, the error should not occur (unless the target OS is not currently supported).
For dependency errors on Linux systems first check the required Glibc versions for each supported OS at this url:
The customer was provided with and deployed the latest (new) version of the Infrastructure Manager (IM) for 20.4 which is included in CU5 and that resolved the issue.
If UIM 20.4 CU5 is installed the new IM will be located in the /nimsoft/install/setup folder.
The only way to obtain it is to upgrade to CU5, which puts a new NimbusManager.exe at /nimsoft/install/setup which is also the same location that the Primary hub /uimhome page references.