Versions Compared

Version Old Version 23 New Version 24
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

Troubleshooting Queries

Warning

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 

the history.t_ConnectionHistory

 table

 table.


Provide steps that the user can take to solve the problem. For example "The level 7 printer will flash red when it is out of paper. Add paper to tray 1".

Panel
bgColor#fff
  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"

...