Troubleshooting

This topic describes common problems that occur with the session sensor and presents solutions for those problems.

CTJTD0591W Session IP not found within discovered IP interfaces

Problem
The IP being discovered does not actually exist in the interface list of the object.
Usually this means the object being discovered is a load balancer. Discovering load balancers can lead to over-merges. For example, if you have three computers behind the load balancer, the ssh requests from the sensor may go to different targets each time. This would result in all three computers merging over time.
Solution
A new property has been added to the session sensor:
com.collation.discover.agent.sys.SessionSensor.loadBalancerIp
The default is false.
If set to true, then this property stops the session sensor if it senses this condition.
Note: After the failure of the session sensor, the SnmpSensor will not be triggered either.

Sensors fails with access denied error message

Problem
During a discovery of Windows Server 2012 with User Account Control turned on, the following error message is displayed:
CTJTP1163E The following WMI session and SSH sessions cannot be established (WMI: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied.
Solution
This message indicates that User Account Control settings are too restrictive. To fix the problem, complete the following steps:
  1. On the target machine, run the Registry Editor, Regedit.exe.
  2. Set the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System LocalAccountTokenFilterPolicy value to 1.
  3. In the Control Panel window, click the Administrative Tools tab and open Local Security Policy.
  4. Expand Local Policies and click Security Options.
  5. Change the following policies:
    • Set the Behavior of the elevation prompt for administrators in Admin Approval Mode policy to Elevate without Prompting.
    • Set the User Account Control: Detect application installations and prompt for elevation policy to Disabled.
In order to configure policies on the system with Active Directory, complete the following steps:
  1. In the Control Panel window, click the Administrative Tools tab and open Group Policy Management.
  2. Choose forest and domain and select Default Domain Policy.
  3. Click Action > Edit.
  4. Open Computer Configuration/Policies/Windows Settings/Security Settings/Local Policies/Security options.
  5. Change the following policies:
    • Set the Behavior of the elevation prompt for administrators in Admin Approval Mode policy to Elevate without Prompting.
    • Set the User Account Control: Detect application installations and prompt for elevation policy to Disabled.

SSH discovery of Windows target with Tectia SSH Server fails with the invalid virtual path error

Problem
The SSH discovery of a Windows system fails, and the log files contain the following message:
java.io.IOException: SSHSCP1.readResponse, error: scp: invalid virtual path
Solution
Tectia SSH Server supports virtual folders. It is possible to remove all default virtual folders named C:, D:, E:, and so on, and to define virtual folders named C, D, E, and so on. In such case, full paths with colons in name, for example /C:/folder/example.txt, are not accepted by the server. To solve this problem, complete one of the following steps:
  • Modify Tectia SSH Server configuration by defining virtual folders with colons.
  • Add the following scoped property to the collation.properties file:
    com.ibm.cdb.session.tectia.filepath.removeColon=true
    You can define the preceding flag only for the selected IPs and scope sets. For example:
    com.ibm.cdb.session.tectia.filepath.removeColon.10.11.12.13=true
com.ibm.cdb.session.tectia.filepath.removeColon.scopesetA=true

The application cannot establish the WMI session

Problem
The following warning message can be found in the SessionSensor logs:
SessionSensor-10.4.112.196-[445,135] WARN engine.AgentRunner -
[AgentRunner.W.1] AgentException thrown in agent
com.collation.discover.agent.AgentException: CTJTP1161E The application
cannot establish the following WMI session: SessionClientException:
Uncaught exception invoking InstallProvider: System.
NullReferenceException: Object reference not set to an instance of an
object.
Solution
To define the cause of the problem, complete the following steps:
  1. Test WMI locally by running simple queries, to see whether it returns any data.
  2. Run the following WMI verifyrepository command:
    Winmgmt  /verifyrepository
If simple queries do not return any results, or if the verifyrepository command is corrupted, the cause of the problem is WMI repository. If the verifyrepository command fails, a local server administrator must rebuild the local WMI repository or recompile it completely from files on the server. If it does not resolve the problem, further investigation is necessary.

The RPC server is unavailable error occurs during discovery with the session sensor

Problem
When you run a discovery by using the session sensor, the following error occurs:
The RPC server is unavailable. (Exception from HRESULT:0x800706BA>
Solution
Check whether the reverse DNS lookup function works properly for the failing target. Run the following command from the Agile Service Manager discovery server, or the anchor server:
nslookup target-IP-address
Check if the IP address of the target is correctly mapped to its FQDN name.