The Azure Advanced Threat Protection Sensor service terminated unexpectedly

%3CLINGO-SUB%20id%3D%22lingo-sub-1416995%22%20slang%3D%22en-US%22%3EThe%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1416995%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CFONT%3EThe%20Azure%20ATP%20agent%20installation%20was%20performed%20on%20the%20domain%20controllers%2C%20the%20installation%20of%20the%20sensors%20is%20successful%2C%20however%2C%20we%20noticed%20that%20the%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20does%20not%20start%20and%20remains%20in%20the%20status%20of%20Starting%3CBR%20%2F%3EReviewing%20the%20System%20events%20shows%20us%20many%20errors%20of%20Service%20Control%20Manager%20ID%207031%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly.%20It%20has%20done%20this%20%23%20times.%20The%20following%20corrective%20action%20will%20be%20taken%20in%205000%20milliseconds.%20Restart%20the%20service.%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3EChecking%20the%20Azure%20Advanced%20Threat%20Protection%20error%20logs%20we%20find%20the%20following%3A%3CBR%20%2F%3EMicrosoft.Tri.Sensor-Errors%3A%3CBR%20%2F%3E2020-05-25%2022%3A22%3A01.7532%20Error%20DirectoryServicesResolver%2B%3CCREATEDOMAINASYNC%3Ed__126%20System.NullReferenceException%3A%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CDOMAIN%3E%20Microsoft.Tri.Sensor.DirectoryServicesResolver.CreateDomainAsync(DistinguishedName%20distinguishedName%2C%20Guid%20domainControllerConfigurationGuid)%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CIREADONLYCOLLECTION%3E%3CDOMAIN%3E%26gt%3B%20Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()%2B(%3F)%20%3D%26gt%3B%20%7B%20%7D%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CIREADONLYCOLLECTION%3E%3CTDESTINATIONITEM%3E%26gt%3B%20Microsoft.Tri.Infrastructure.EnumerableExtension.SelectAsync%3CTSOURCEITEM%3E(IEnumerable%3CTSOURCEITEM%3E%20enumerable%2C%20Func%3CTSOURCEITEM%3E%26gt%3B%20selectorAsync)%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CIREADONLYCOLLECTION%3E%3CDOMAIN%3E%26gt%3B%20Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Sensor.DirectoryServicesResolver.OnStartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.Module.StartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.ModuleManager.OnStartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.Module.StartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.Service.OnStartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20void%20Microsoft.Tri.Infrastructure.TaskExtension.Await(Task%20task)%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20void%20Microsoft.Tri.Infrastructure.Service.OnStart(string%5B%5D%20args)%3C%2FDOMAIN%3E%3C%2FIREADONLYCOLLECTION%3E%3C%2FTSOURCEITEM%3E%3C%2FTSOURCEITEM%3E%3C%2FTSOURCEITEM%3E%3C%2FTDESTINATIONITEM%3E%3C%2FIREADONLYCOLLECTION%3E%3C%2FDOMAIN%3E%3C%2FIREADONLYCOLLECTION%3E%3C%2FDOMAIN%3E%3C%2FCREATEDOMAINASYNC%3E%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EMicrosoft.Tri.Sensor.Updater-Errors%3A%3CBR%20%2F%3E2020-05-21%2010%3A53%3A27.7922%20Error%20ServiceControllerExtension%20ChangeServiceStatus%20failed%20to%20change%20service%20status%20%5Bname%3DAATPSensor%20status%3DRunning%20Exception%3DSystem.ServiceProcess.TimeoutException%3A%20Time%20out%20has%20expired%20and%20the%20operation%20has%20not%20been%20completed.%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus%20desiredStatus%2C%20TimeSpan%20timeout)%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Tri.Infrastructure.ServiceControllerExtension.ChangeServiceStatus(String%20name%2C%20ServiceControllerStatus%20status%2C%20TimeSpan%20timeout%2C%20Nullable%601%20awaitedStatus)%5D%3CBR%20%2F%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1417153%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1417153%22%20slang%3D%22en-US%22%3EWhat%20is%20the%20exact%20version%20of%20the%20sensor%3F%20You%20can%20check%20by%20the%20name%20of%20the%20folder%20the%20binary%20is%20in...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1417666%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1417666%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F106935%22%20target%3D%22_blank%22%3E%40Eli%20Ofek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20version%20of%20the%20sensor%20is%202.114.8044.7220.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1418699%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1418699%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F679403%22%20target%3D%22_blank%22%3E%40ISEGOVIA%3C%2FA%3E%26nbsp%3B.%20Telemetry%20shows%20this%20error%20happens%20on%205%20sensors%2C%20all%20of%20them%20belonging%20to%20the%20same%20workspace%20(probably%20yours%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3EThis%20is%20unknown%20issue%2C%20and%20too%20complex%20to%20resolve%20over%20the%20forums%20as%20it%20will%20require%20exchanging%20sensitive%20info.%3C%2FP%3E%0A%3CP%3EI%20strongly%20suggest%20to%20open%20a%20support%20ticket%20to%20handle%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEli.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1444132%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1444132%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F106935%22%20target%3D%22_blank%22%3E%40Eli%20Ofek%3C%2FA%3E%3A%3C%2FP%3E%3CP%3EAs%20you%20suggested%2C%20we%20put%20together%20a%20premier%20support%20case%20for%20analysis%20of%20the%20incident%20presented.%20I%20tell%20you%20that%20we%20were%20recommended%20to%20create%20and%20use%20a%20gMSA%20account%20in%20the%20environment.%20This%20account%20was%20generated%20according%20to%20the%20documentation%2C%20also%2C%20it%20was%20validated%20that%20all%20the%20communication%20ports%20necessary%20for%20the%20service%20will%20be%20open%2C%20the%20use%20of%20wireshark%20in%20DCs%20was%20ruled%20out%20and%20the%20sensor%20version%20was%20updated%20to%202.115.8077%2C%20however%20the%20Azure%20ATP%20service%20continues%20without%20starting.%26nbsp%3B%3C%2FP%3E%3CP%3ELogs%20only%20show%20us%20the%20following%20errors%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EMicrosoft.Tri.Sensor.Updater%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CFONT%3E2020-06-03%2019%3A34%3A27.1581%20Error%20ServiceControllerExtension%20ChangeServiceStatus%20failed%20to%20change%20service%20status%20%5Bname%3DAATPSensor%20status%3DRunning%20Exception%3DSystem.ServiceProcess.TimeoutException%3A%20Time%20out%20has%20expired%20and%20the%20operation%20has%20not%20been%20completed.%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus%20desiredStatus%2C%20TimeSpan%20timeout)%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Tri.Infrastructure.ServiceControllerExtension.ChangeServiceStatus(String%20name%2C%20ServiceControllerStatus%20status%2C%20TimeSpan%20timeout%2C%20Nullable%601%20awaitedStatus)%5D%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3E%3CSTRONG%3EMicrosoft.T%3C%2FSTRONG%3E%3CSTRONG%3Eri.Sensor-Errors%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E2020-06-03%2019%3A38%3A08.2531%20Error%20DirectoryServicesResolver%2B%3CCREATEDOMAINASYNC%3Ed__130%20System.NullReferenceException%3A%20Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CDOMAIN%3E%20Microsoft.Tri.Sensor.DirectoryServicesResolver.CreateDomainAsync(DistinguishedName%20distinguishedName%2C%20Guid%20domainControllerConfigurationGuid)%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CIREADONLYCOLLECTION%3E%3CDOMAIN%3E%26gt%3B%20Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()%2B(%3F)%20%3D%26gt%3B%20%7B%20%7D%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CIREADONLYCOLLECTION%3E%3CTDESTINATIONITEM%3E%26gt%3B%20Microsoft.Tri.Infrastructure.EnumerableExtension.SelectAsync%3CTSOURCEITEM%3E(IEnumerable%3CTSOURCEITEM%3E%20enumerable%2C%20Func%3CTSOURCEITEM%3E%26gt%3B%20selectorAsync)%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%3CIREADONLYCOLLECTION%3E%3CDOMAIN%3E%26gt%3B%20Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Sensor.DirectoryServicesResolver.OnStartAsync()%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.Module.StartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.ModuleManager.OnStartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.Module.StartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20async%20Task%20Microsoft.Tri.Infrastructure.Service.OnStartAsync()%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20void%20Microsoft.Tri.Infrastructure.TaskExtension.Await(Task%20task)%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20void%20Microsoft.Tri.Infrastructure.Service.OnStart(string%5B%5D%20args)%3C%2FDOMAIN%3E%3C%2FIREADONLYCOLLECTION%3E%3C%2FTSOURCEITEM%3E%3C%2FTSOURCEITEM%3E%3C%2FTSOURCEITEM%3E%3C%2FTDESTINATIONITEM%3E%3C%2FIREADONLYCOLLECTION%3E%3C%2FDOMAIN%3E%3C%2FIREADONLYCOLLECTION%3E%3C%2FDOMAIN%3E%3C%2FCREATEDOMAINASYNC%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EThanks%20for%20your%20help.%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1444165%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1444165%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F679403%22%20target%3D%22_blank%22%3E%40ISEGOVIA%3C%2FA%3E%26nbsp%3BI%20am%20working%20with%20the%20escalation%20engineer%20on%20this%20one.%20I%20got%20to%20take%20a%20look%20at%20the%20dumps%20collected%20today%20a%20few%20minutes%20ago%20and%20found%20an%20interesting%20insight%20about%20the%20possible%20root%20cause.%3CBR%20%2F%3ESince%20it%20involves%20specific%20domain%20information%2C%20support%20will%20elaborate%20on%20what%20was%20found%20and%20what%20to%20check%20next.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1451932%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1451932%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F106935%22%20target%3D%22_blank%22%3E%40Eli%20Ofek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20comment%20that%20reviewing%20the%20Azure%20ATP%20portal%20today%20we%20can%20see%20that%20one%20of%20the%20sensors%20is%20already%20running%20correctly%20and%20the%20Azure%20ATP%20tool%20is%20already%20starting%20to%20report%20information%20from%20the%20environment.%3CBR%20%2F%3EHowever%20the%20other%20sensors%20still%20continue%20in%20starting.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20attach%20the%20evidence.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452006%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Azure%20Advanced%20Threat%20Protection%20Sensor%20service%20terminated%20unexpectedly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452006%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F106935%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40Eli%20Ofek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20comment%20that%20reviewing%20the%20Azure%20ATP%20portal%20today%20we%20can%20see%20that%20one%20of%20the%20sensors%20is%20already%20running%20correctly%20and%20the%20Azure%20ATP%20tool%20is%20already%20starting%20to%20report%20information%20from%20the%20environment.%3CBR%20%2F%3EHowever%20the%20other%20sensors%20still%20continue%20in%20starting.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20attach%20the%20evidence.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor
The Azure ATP agent installation was performed on the domain controllers, the installation of the sensors is successful, however, we noticed that the Azure Advanced Threat Protection Sensor service does not start and remains in the status of Starting
Reviewing the System events shows us many errors of Service Control Manager ID 7031 The Azure Advanced Threat Protection Sensor service terminated unexpectedly. It has done this # times. The following corrective action will be taken in 5000 milliseconds. Restart the service.
 
Checking the Azure Advanced Threat Protection error logs we find the following:
Microsoft.Tri.Sensor-Errors:
2020-05-25 22:22:01.7532 Error DirectoryServicesResolver+<CreateDomainAsync>d__126 System.NullReferenceException: Object reference not set to an instance of an object.
   at async Task<Domain> Microsoft.Tri.Sensor.DirectoryServicesResolver.CreateDomainAsync(DistinguishedName distinguishedName, Guid domainControllerConfigurationGuid)
   at async Task<IReadOnlyCollection<Domain>> Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()+(?) => { }
   at async Task<IReadOnlyCollection<TDestinationItem>> Microsoft.Tri.Infrastructure.EnumerableExtension.SelectAsync<TSourceItem, TDestinationItem>(IEnumerable<TSourceItem> enumerable, Func<TSourceItem, Task<TDestinationItem>> selectorAsync)
   at async Task<IReadOnlyCollection<Domain>> Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()
   at async Task Microsoft.Tri.Sensor.DirectoryServicesResolver.OnStartAsync()
   at async Task Microsoft.Tri.Infrastructure.Module.StartAsync()
   at async Task Microsoft.Tri.Infrastructure.ModuleManager.OnStartAsync()
   at async Task Microsoft.Tri.Infrastructure.Module.StartAsync()
   at async Task Microsoft.Tri.Infrastructure.Service.OnStartAsync()
   at void Microsoft.Tri.Infrastructure.TaskExtension.Await(Task task)
   at void Microsoft.Tri.Infrastructure.Service.OnStart(string[] args)
 
Microsoft.Tri.Sensor.Updater-Errors:
2020-05-21 10:53:27.7922 Error ServiceControllerExtension ChangeServiceStatus failed to change service status [name=AATPSensor status=Running Exception=System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
   at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
   at Microsoft.Tri.Infrastructure.ServiceControllerExtension.ChangeServiceStatus(String name, ServiceControllerStatus status, TimeSpan timeout, Nullable`1 awaitedStatus)]
6 Replies
Highlighted
What is the exact version of the sensor? You can check by the name of the folder the binary is in...
Highlighted

Hi @Eli Ofek 

 

The version of the sensor is 2.114.8044.7220.

 

Thanks for your support.

Highlighted

@ISEGOVIA . Telemetry shows this error happens on 5 sensors, all of them belonging to the same workspace (probably yours :)

This is unknown issue, and too complex to resolve over the forums as it will require exchanging sensitive info.

I strongly suggest to open a support ticket to handle it.

 

Eli.

Highlighted

Hi @Eli Ofek:

As you suggested, we put together a premier support case for analysis of the incident presented. I tell you that we were recommended to create and use a gMSA account in the environment. This account was generated according to the documentation, also, it was validated that all the communication ports necessary for the service will be open, the use of wireshark in DCs was ruled out and the sensor version was updated to 2.115.8077, however the Azure ATP service continues without starting. 

Logs only show us the following errors:

 

Microsoft.Tri.Sensor.Updater

2020-06-03 19:34:27.1581 Error ServiceControllerExtension ChangeServiceStatus failed to change service status [name=AATPSensor status=Running Exception=System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
   at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
   at Microsoft.Tri.Infrastructure.ServiceControllerExtension.ChangeServiceStatus(String name, ServiceControllerStatus status, TimeSpan timeout, Nullable`1 awaitedStatus)]

 

Microsoft.Tri.Sensor-Errors

2020-06-03 19:38:08.2531 Error DirectoryServicesResolver+<CreateDomainAsync>d__130 System.NullReferenceException: Object reference not set to an instance of an object.
   at async Task<Domain> Microsoft.Tri.Sensor.DirectoryServicesResolver.CreateDomainAsync(DistinguishedName distinguishedName, Guid domainControllerConfigurationGuid)
   at async Task<IReadOnlyCollection<Domain>> Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()+(?) => { }
   at async Task<IReadOnlyCollection<TDestinationItem>> Microsoft.Tri.Infrastructure.EnumerableExtension.SelectAsync<TSourceItem, TDestinationItem>(IEnumerable<TSourceItem> enumerable, Func<TSourceItem, Task<TDestinationItem>> selectorAsync)
   at async Task<IReadOnlyCollection<Domain>> Microsoft.Tri.Sensor.DirectoryServicesResolver.GetDomainsAsync()
   at async Task Microsoft.Tri.Sensor.DirectoryServicesResolver.OnStartAsync()
   at async Task Microsoft.Tri.Infrastructure.Module.StartAsync()
   at async Task Microsoft.Tri.Infrastructure.ModuleManager.OnStartAsync()
   at async Task Microsoft.Tri.Infrastructure.Module.StartAsync()
   at async Task Microsoft.Tri.Infrastructure.Service.OnStartAsync()
   at void Microsoft.Tri.Infrastructure.TaskExtension.Await(Task task)
   at void Microsoft.Tri.Infrastructure.Service.OnStart(string[] args)

 

Thanks for your help.

Highlighted

@ISEGOVIA I am working with the escalation engineer on this one. I got to take a look at the dumps collected today a few minutes ago and found an interesting insight about the possible root cause.
Since it involves specific domain information, support will elaborate on what was found and what to check next.

Highlighted

Hi @Eli Ofek 


I comment that reviewing the Azure ATP portal today we can see that one of the sensors is already running correctly and the Azure ATP tool is already starting to report information from the environment.
However the other sensors still continue in starting. 

 

I attach the evidence.

 

Thanks for your help.