Scense Administrator Guide

  1. Home
  2. Docs
  3. Scense Administrator Guid...
  4. Troubleshooting
  5. Scense Diagnostic Tool

Scense Diagnostic Tool

In case there’s doubt whether or not the Scense Engine Service is functioning properly, Scense_Diag.exe can be used to run some tests.

The ‘leds’ within Scense_Diag indicate if the server components are functioning properly.
Scense_Diag will show detailed information if the option ‘Advanced’ is selected.

The information of Scense_Diag can best be compared with a Ping task.
In case one of the interfaces is not functioning the descriptive message Scense_Diag provides may be key to the cause of the problem.

Engine performance through ScenseDiag

The example above shows the creation of the Scense Engine object takes 442 milliseconds the first time. A succeeding time this will be considerably less (70 to 80 milliseconds)

Furthermore it can be seen that for the ‘roundtrip’ part an internal response time of 2 ms is measured, while the external response takes 42 Ms. It can be concluded the overhead for this procedure-call takes 40 ms (network and service time).

The other two procedure-calls show how much time is needed to read data from the database (data_access: 16 ms) and how long it takes to request information from the Active Directory (ntds_access: 9 ms)

In this manner the response time of the Scense Engine can be measured quite precisely, and possible ‘bottlenecks’ can be detected.

The other sections show the various UNC network paths being checked.
These paths are defined in the Site objects, and represent installer paths and repository paths.