Troubleshooting Discovery

This section contains basic troubleshooting procedures for Discovery. For more information, see Common Discovery Issues.

After you install Discovery, we recommend that you use the following steps to ensure that all relevant services are properly installed and working correctly.

We recommend resetting the logs back to the error log level after troubleshooting is completed. Otherwise, the application will continue to generate large logs that contain a high level of detail.

The following table describes the available logs, their location and the type of information they contain in order to troubleshoot an issue.

Log Type Log Name For Issues
Client or Gateway JobQueue_GetClientTasksQueue.log GetClientTask
JobQueue_OutboxProcessorTasksQueue.log ClientTransport (send Audits to Server)
JobQueue_DiscoCtrlTasksQueue.log Discovery Task Queue
UpdateCheckThread_*.log Binary Update
SaaSClientInstallation_*.log Client Installation
JobQueue_AuditTriggerQueue Audit or Remote Scan
JobQueue_ConfigChangeQueue Inventory/Gateway Settings update
Gateway JobQueue_NetScanTasksQueue.log Netscan task processing
JobQueue_VmhaTasksQueue.log VMHA Audit
SaaSGatewayInstallation_*.log Gateway Installation log
NetScanner.log Netscan log
JobQueue_ADScanQueue Active Directory scan log
Server Logs AssetProcessor.frslog Asset processor
AgentTaskWS.frslog Agent Task
ClientTransportProcessorWs.frslog Client Processor
TaskProcessor.frslog Task Processor
DiscoProcessor.frslog Discovery Message Processor
MessageQueueService.frslog Message Queue Service

Discovery Troubleshooting Basics

1.From the main server, check that all services are running correctly by doing the following:

a. Click a service such as AgentTaskWs.
b. In the Content window, right-click on the ASMX file.
c. Right-click and select Browse....
d. Check if the agent task is responding. If it is, it opens a new window that lists the supported operations.
e. Follow the same steps with the ClientTransportProcessor service.

2.For App services, check that Net.tcp is up and running.

a. From a command window (as administrator) run a telnet client on the server name using the specified net.tcp port configuration.
b. Enter a specific domain name or IP address such as C:\Windows\System32\telnet Domain_Name_IP_Address 7100.

If net.tcp is correctly configured, the application displays a Telnet command window with no data.

3.Check the log file on the client or gateway machine for errors. The log file path is usually ~\FRS\Logs\JobQueues. Any errors appear in the GetClientTask job. An example of a file name is JobQueue_GetClientTasksQueue_00000037014.

4.Check the Netscan tasks queue log file for errors. An example of a file name is JobQueue_NetScanTasksQueue_00000 000058.

5.Check the AssetProcessor.log file (the server log) located under ~\Logs for any errors.