Troubleshooting
Problem
Symptom
Resolving The Problem
The following information describing the problem and the environment
- The error message
- The time of the error
- A screenshot showing the problem
- The IP of the target server
- The IP of the Windows Gateway
- Whether any anchor servers are configured in the environment and whether the discovery goes through them.
- The TADDM version
- The target server version
Logs
In order to gather the appropriate logs, please ensure that TADDM logging is in DEBUG and that split sensor logging is enabled. You can confirm or change these settings in dist/etc/collation.properties:
com.collation.log.level=DEBUG
com.collation.discover.engine.SplitSensorLog=true
If the SplitSensorLog setting is changed you will need to restart TADDM.
Change the below properties in collation.properties file:
com.collation.log.level.vm.Discover=DEBUG
com.collation.log.level.vm.DiscoverAdmin=DEBUG
com.collation.log.level.vm.DiscoveryService=DEBUG
If either setting is changed, please reproduce before gathering logs.
Then please gather up the following logs.
$COLLATION_HOME/dist/log/*
$COLLATION_HOME/dist/log/services/*
$COLLATION_HOME/dist/log/sensors/*/*
If an anchor server is involved, please also gather the logs files in the taddm7.3.*/log directory in the anchor service account's home directory on the anchor server.
On UNIX systems we recommend using "tar -cvfz" to product a tar + zipped collection of logs. A zip file is sufficient for Windows. Please name the file with the full PMR number (i.e. 21014,082,000.tar.gz) and either upload them via the support website, email them to tivoli_support@ecurep.ibm.com (make sure the full pmr # is in the subject line) or ftp to ftp.ecurep.ibm.com /toibm/tivoli.
Tests
Do you have appropriate access on the target server?
Test 1 - Run wmimgmt.msc
Use the Microsoft WMI Control Console ( wmimgmt.msc ) on the gateway to
connect to the failing target.
Log in as the user you specified in the access list for Windows discoveries.
Once logged in you can select Properties from the Action list and display system information from the target.
Send a screenshot of the Properties popup.
If wmimgmt.msc runs successfully move on to the next test.
If it fails, have your Windows admin investigate the WMI problem.
Some possible causes
- .NET 1.1 or above not working correctly or missing.
- RPC service not working
- Check the account you are using to make sure it is valid and active.
Test 2 - Run testwmi
The testwmi tool in dist/support/bin, must be launched on the TADDM server and uses TADDM's scope and access list to contact the target. It must authenticate with a TADDM administrative ID and password.
For example: testwmi.bat -u administrator -p collation <ip address>
If there are authentication problems you should see entries in the SecurityManager.log in dist/log/services.
Please note that all tools provided in dist/support/bin are not officially supported. These are diagnostic tools that are only used for troubleshooting. It should not be used as a part of your production environment.
Test 3 - Run wmidiag
Executing remote WMI queries like TADDM does during discovery takes a certain level of access. Microsoft has a tool called "wmidiag" that will verify that the target server has the access we need.
You can download the tool from Microsoft at the following URL:
http://www.microsoft.com/download/en/details.aspx?id=7684
Please run the tool on the target server as the user TADDM is using for discovery.
Running WMIDiag produces three files, by default in the %TEMP% directory. Review and/or send TADDM support two of them:
- .log file containing a verbose output of the WMIDiag tool activity.
- .txt file containing a summarized report with warnings and errors worthy of investigation.
• .csv file containing statistics that can be used to measure trends in WMI issues over time.
Test 4 WBEMTEST
WBEMTEST.exe is included on every computer that has WMI installed. It can be used to explore or confirm WMI details. For more information on running WBEMTEST go to:
--------Wbemtest execution steps-------
1.Go to Window target server
2.Press window+r
3.Enter cmd(command prompt will open)
4.Type wbemtest
5.GUI will pop-up
6.When testing from gateway use IP of the target in place of "target IP" in "\\<target IP>\root\cimv2" Namespace, enter the credentials and click "connect" on right most corner. when directly on target, use "\root\cimv2" in Namespace
7.Under IWbemServices, click on Query
8.Enter the query e.g. "SELECT BuildVersion FROM Win32_WMISetting", click apply.
Note: Query(for which o/p needs to be verified) can be found in the sensor log of session or window computer system.
9.Double click on the result in the result window to display the actual o/p.
Related Information
Product Synonym
TADDM
Was this topic helpful?
Document Information
Modified date:
06 December 2023
UID
swg21426185