Verify Process Discovery Sensor Installation

Use the log files to verify that the Process Discovery Sensor is installed correctly on your machine.

Procedure

  1. While the Process Discovery Sensor is running and in recording mode, click a few times anywhere on your machine.
    Clicking a few times on your machine triggers the Process Discovery Sensor to collect and send a screenshot to the Platform which results in entries in the Process Discovery Sensor logs that you can use for validation.
    For more details on enabling the Process Discovery Sensor in recording mode, see Enable and disable the users recording.
  2. From Windows Explorer, open the C:\Users\<username>\AppData\Local\Programs\Neo2 folder. If you changed the default location for the logs, then open the folder you have changed it to.
  3. Locate this log file: Neo_<machine name>_<userid>.log
  4. Double-click to open the log file.
    If the Process Discovery Sensor is working as expected, the following lines display as an example towards the bottom of the log file. If everything is correct, a job number displays, followed by OK. 
    2022-11-08 22:03:39.3775 TEST\testuser com.FIQ.Neo2.Utility.Network.RawLogForwardingPostConsumer [INFO] Worker id: 5b1bd418-2e19-4097-8ba7-31af6f22bd0a, queue size: 0, current job 152 OK, time elapsed: 0ms, type: fiq.win.keylog
    2022-11-08 22:03:39.3775 TEST\testuser com.FIQ.Neo2.Utility.Network.RawLogForwardingPostConsumer [INFO] Worker id: 61849714-b916-43b7-8878-eced56dd1d65, queue size: 0, current job 151 OK, time elapsed: 5ms, type: fiq.win.screenshot
    If the Process Discovery Sensor is not working, you will see words such as error and failed in the log files output.
    Note: If you experience issues, please contact Automation Anywhere for assistance. 
    2022-11-08 14:13:32.5720 TEST\testuser com.FIQ.Neo2.Utility.Network.RawLogForwardingPostConsumer [ERROR] Worker id: bbe8547d-3c67-473d-a328-e949a7c25a03, queue size: 13, current job 2 failed, type: fiq.win.screenshot, time elapsed: 10ms, System.AggregateException: One or more errors occurred. ---> Flurl.Http.FlurlHttpException: Call failed. An error occurred while sending the request. POST https://test.example.com:443/fiq.win.screenshot ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'test.example.com'