Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Problem

In large estates, the iQSonar user interface can sometimes be slow to respond and/or display so much information as to be unwieldy to use. In these circumstances it can be useful to run diagnostic queries against the database directly rather than attempting to rely only on the iQSonar UI to discover why certain targets were not scanned and to make any needed changes to the scan engine configuration or to the targets to enable them to be scanned.

Prerequisites

In order to use these scripts, you will need credentials to log in to the SQL server that hosts the iQSonar database. You will require permissions to run queries and, in some cases to execute stored procedures.

You will need to have access to the Microsoft SQL Server Management Studio software. The current version (at time of writing version 17) is a free-of-charge download from Microsoft.
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017

You need to understand how to edit the SQL queries. Most of them contain placeholder values for ProjectID, Date(s) and/or IP Addresses which will need to be updated to work in your specific environment. If you do not update these values, the queries will not run, or will return meaningless results.

Troubleshooting Queries

These queries work with iQSonar releases up to and including Fu R3.
Some of them do NOT work with iQSonar Gwynn R1 or later due to changes to the history.t_ConnectionHistory table.


  1. One Line troubleshooting scripts
  2. Get list of Project IDs (required for many queries)
  3. List all Found Devices
  4. Use SQL to send a target for a rescan
  5. Find unreachable targets
  6. Summary of connection attempt results
  7. Connection Results for specific target
  8. Find hosts with SSH Login failures
  9. Find hosts with Windows login failures
  10. Find ESX hosts that were not scanned
  11. Find hosts that could not be scanned for other reasons.
  12. Database Credential Issues
  13. All credential issues
  14. List all discovered databases (scanned and unscanned)
  15. List all commands performed during a scan
  16. Some targets seem stuck in "Waiting"



  • No labels