Troubleshooting
Problem
Window's target scan is failing due to wrong wmi version
Symptom
Getting the following error in the logs:
Getting error:
2013-02-20 15:59:45,476 DiscoverManager [DiscoverWorker-21]
SessionSensor-30.xx.xxx.xx-[445,135,22]-#1 ERROR anchor.AnchorClient -
CTJTD2108E The error, CTJTD2120E An error has occurred in the discovery
process.:CTJTP1163E The following WMI session and SSH sessions cannot be
established (WMI: WMI provider file TaddmWmi.dll version could not be
determined (Invalid namespace), and we have already tried to autodeploy
and restart WMI; SSH: CTJTP1190E The server did not complete the
authorization process. )., occurred for the following remote server:
30.xxx.xx.xx
Cause
The issue was that the TaddmWmi.dll version was wrong and needed to be replaced.
Resolving The Problem
Starting of troubleshooting, It is always good to check the WMI settings in collation.properties to make sure that auto deploy and RestartWmiOnFailure equals to true.
# Should WindowsOs autodeploy the Win32_Confignia WMI provider?
com.collation.platform.os.WindowsOs.AutoDeploy=true
# Restart WMI if a WMI error is encountered during AutoDeploy
com.collation.RestartWmiOnAutoDeploy=true
com.collation.RestartWmiOnAutoDeploy.1.2.3.4=true
# Restart WMI if a WMI error is encountered (except during AutoDeploy)
com.collation.RestartWmiOnFailure=true
com.collation.RestartWmiOnFailure.1.2.3.4=true
For this example, after checking the target, found that the TaddmWmi.dll had a newer timestamp, but was a older version than the one provided by the taddm scan.
If the timestamp of the dll file is newer, even if the version itself is older, this will have to be fixed manually via deleting the TaddmWmi.dll currently in place on the target.
Here are the conditions under which the TaddmWmi.dll gets redeployed. It is based on a timestamp as follows:
- if the timestamp from the TaddmWmi.dll on the gateway is "newer" than the timestamp from the TaddmWmi.dll on the endpoint, then the DLL, MOF, and PDB (symbol file) files are copied to the endpoint. (We do not check the timestamp of the MOF file or symbol file)
- if the timestamp from the TaddmWmi.exe on the gateway is
"newer" than the timestamp from the TaddmWmi.exe on the endpoint, the the EXE is copied to the endpoint.
Product Synonym
TADDM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21626703