Feb 28 2023 01:03 AM - edited Feb 28 2023 01:04 AM
Hi all, I have a customer running multiple AD Domain Controllers on windows server 2012, 2016 and 2019. ATP sensor version 2.197.16100.44617 was working fine, but a few days ago it started automatic upgrade to 2.198.16173.18440, the new sensor service "Azure Advanced Threat Protection Sensor" cannot start. Application event log also shows a variety of error messages from soure 'Perflib'. This is new, as the 2012 domain controllers were working fine and had no errors in Application log prior to ATP Sensor upgrade. Has anybody experienced the same issue?
PS1: the new ATP sensor version on windows 2016 and 2019 domain controllers works fine.
PS2: windows 2012 servers running january and february patches.
-Ruslan
Feb 28 2023 01:29 AM
Feb 28 2023 01:59 AM
@RNalivaika Check the sensor local logs to looks for errors about what is failing it.
https://learn.microsoft.com/en-us/defender-for-identity/troubleshooting-using-logs
If possible paste here the failing call stack and error message.
Another option is to open a support case (might be faster...)
Feb 28 2023 02:08 AM
Feb 28 2023 02:39 AM
Mar 08 2023 04:33 AM
working with ms support is anything other than fast :) sent them logs more than a week ago, still zero progress...
Mar 08 2023 05:06 AM
Hi @RNalivaika,
What was the solution?
I had similar one some time ago.
Error ServiceControllerExtension Failed to change service status [name=AATPSensor status=Running Exception=System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
Microsoft.Tri.Sensor-Errors.log file pointed to an error with the WinPcap or NPF driver.
As WinPcap is no longer supported then probably Npcap could be re-installed.
Mar 08 2023 07:22 AM
SolutionMar 16 2023 01:32 AM
@Eli Ofekthe service is starting successfully after update to version 2.199.16251.32043
Mar 16 2023 01:35 AM