Forum Discussion
AATPSensor Service stuck in starting process
- Apr 01, 2019
Hi, finally after some days (about 3) the AATP was able to create the Microsoft.Tri.Sensor-Errors.log file and pointed me to an error with the WinPcap or NPF driver.
Just reinstalled the WinPcap driver, rebooted the server and voila the AATP Sensor started running like charm!
***** This needs to be added to the support/troubleshoot documentation as the AATP error log took days to generate the error log and hence if it's already as an option for users to verify in advanced, users like me would tackle this right away*****
Hi, finally after some days (about 3) the AATP was able to create the Microsoft.Tri.Sensor-Errors.log file and pointed me to an error with the WinPcap or NPF driver.
Just reinstalled the WinPcap driver, rebooted the server and voila the AATP Sensor started running like charm!
***** This needs to be added to the support/troubleshoot documentation as the AATP error log took days to generate the error log and hence if it's already as an option for users to verify in advanced, users like me would tackle this right away*****
JCordova Can you explain - how come only after 3 days you saw the log?
Wasn't the file created from the first crash? I was under the impression it was, but you previously looked in another file...
- JCordovaApr 01, 2019Copper ContributorThat was the difficult part of it and I mentioned it on the 3rd paragraph “There is no Microsoft.Tri.Sensor-Errors.log being created...”
So not sure why it took so long to create, but it wasn’t being created.- EliOfekApr 02, 2019
Microsoft
JCordova , Can you share with me (in a private message) your workspace ID, and name of sensor machine (all in text format)?
You can get those form the AATP console UI by pressing on the question mark in the toolbar.
- ZantenBFeb 11, 2022Copper Contributor
Hi all.
Where is this logfile located? I finally was able to install the agent using a scheduled task under 'system' now the agent is started on my physical DC's, but starting on my virtual ones... and no logfile to be found.. Regards, Ben