SOLVED

MDI Sensor service wont start on AD FS server

%3CLINGO-SUB%20id%3D%22lingo-sub-2048479%22%20slang%3D%22en-US%22%3EMDI%20Sensor%20service%20wont%20start%20on%20AD%20FS%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2048479%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20installed%20the%20MDI%20sensor%20on%20one%20of%20my%20AD%20FS%20server%20according%20to%20the%20guide%20but%20the%20service%20will%20not%20start.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAccording%20to%20the%20logs%20it%20through%20the%20following%20exception%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2021-01-11%2011%3A11%3A50.6085%20Error%20Enumerable%20System.InvalidOperationException%3A%20Sequence%20contains%20no%20elements%3CBR%20%2F%3Eat%20TSource%20System.Linq.Enumerable.First%3CTSOURCE%3E(IEnumerable%3CTSOURCE%3E%20source)%3CBR%20%2F%3Eat%20void%20Microsoft.Tri.Sensor.DomainNetworkCredentialsManager.UpdateConfigurations(ConfigurationCollection%20configurations)%3CBR%20%2F%3Eat%20Func%3CTASK%3E%20Microsoft.Tri.Infrastructure.ActionExtension.ToAsyncFunction(Action%20action)%2B(TItem%20_)%20%3D%26gt%3B%20%7B%20%7D%3CBR%20%2F%3Eat%20async%20Task%20Microsoft.Tri.Infrastructure.ConfigurationManager.RegisterConfigurationAsync(Func%3CCONFIGURATIONCOLLECTION%3E%20onConfigurationsUpdateAsync%2C%20Type%5B%5D%20configurationTypes)%3CBR%20%2F%3Eat%20void%20Microsoft.Tri.Infrastructure.TaskExtension.Await(Task%20task)%3CBR%20%2F%3Eat%20object%20lambda_method(Closure%2C%20object%5B%5D)%3CBR%20%2F%3Eat%20object%20Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()%3CBR%20%2F%3Eat%20void%20Microsoft.Tri.Infrastructure.ModuleManager.AddModules(Type%5B%5D%20moduleTypes)%3CBR%20%2F%3Eat%20new%20Microsoft.Tri.Sensor.SensorModuleManager()%3CBR%20%2F%3Eat%20ModuleManager%20Microsoft.Tri.Sensor.SensorService.CreateModuleManager()%3CBR%20%2F%3Eat%20async%20Task%20Microsoft.Tri.Infrastructure.Service.OnStartAsync()%3CBR%20%2F%3Eat%20void%20Microsoft.Tri.Infrastructure.TaskExtension.Await(Task%20task)%3CBR%20%2F%3Eat%20void%20Microsoft.Tri.Infrastructure.Service.OnStart(string%5B%5D%20args)%3C%2FCONFIGURATIONCOLLECTION%3E%3C%2FTASK%3E%3C%2FTSOURCE%3E%3C%2FTSOURCE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20install%20reported%20that%20auditing%20was%20not%20configured%20correctly%20but%20according%20the%20to%20guide%20it%20is%20in%20place%20(I%20can%20see%20the%20events%20in%20the%20security%20log).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20on%20what%20I%20can%20do%20to%20start%20the%20service%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2048479%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eadfs%20mdi%20sensor%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2048502%22%20slang%3D%22en-US%22%3ERe%3A%20MDI%20Sensor%20service%20wont%20start%20on%20AD%20FS%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2048502%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F205276%22%20target%3D%22_blank%22%3E%40Bjarne%20Abraham%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3Ego%20to%20the%20sensor%20list%20in%20MDI%20portal%2C%20click%20on%20this%20new%20sensor%20name%2C%20and%20add%20to%20the%20list%20in%20the%20dialog%20a%20fully%20qualified%20DC%20name%20that%20it%20can%20use%20to%20resolve%20AD%20entities.%3C%2FP%3E%0A%3CP%3Eonce%20that%20it%20should%20start%20fine%20within%20a%20few%20minutes.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2078356%22%20slang%3D%22en-US%22%3ERe%3A%20MDI%20Sensor%20service%20wont%20start%20on%20AD%20FS%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2078356%22%20slang%3D%22en-US%22%3E%3CP%3E%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%3BI'll%20check%20and%20try%20later%20and%20get%20back%2C%20thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2081328%22%20slang%3D%22en-US%22%3ERe%3A%20MDI%20Sensor%20service%20wont%20start%20on%20AD%20FS%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2081328%22%20slang%3D%22en-US%22%3EIt%20worked%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3EI%20was%20not%20able%20to%20see%20this%20in%20the%20install%20guide%3F%3CBR%20%2F%3EAt%20the%20moment%20I've%20added%20two%20DC's%20to%20the%20list%20-%20it%20do%20now%20have%20a%20health%20issue%20towards%20one%20of%20them%20which%20seems%20strange%20as%20the%20sensor%20logs%20indicate%20that%20it's%20communicating%20with%20both%20DCs%20in%20the%20list%3F%3C%2FLINGO-BODY%3E
Occasional Contributor

I've installed the MDI sensor on one of my AD FS server according to the guide but the service will not start.

 

According to the logs it through the following exception:

 

2021-01-11 11:11:50.6085 Error Enumerable System.InvalidOperationException: Sequence contains no elements
at TSource System.Linq.Enumerable.First<TSource>(IEnumerable<TSource> source)
at void Microsoft.Tri.Sensor.DomainNetworkCredentialsManager.UpdateConfigurations(ConfigurationCollection configurations)
at Func<Task> Microsoft.Tri.Infrastructure.ActionExtension.ToAsyncFunction(Action action)+(TItem _) => { }
at async Task Microsoft.Tri.Infrastructure.ConfigurationManager.RegisterConfigurationAsync(Func<ConfigurationCollection, Task> onConfigurationsUpdateAsync, Type[] configurationTypes)
at void Microsoft.Tri.Infrastructure.TaskExtension.Await(Task task)
at object lambda_method(Closure, object[])
at object Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()
at void Microsoft.Tri.Infrastructure.ModuleManager.AddModules(Type[] moduleTypes)
at new Microsoft.Tri.Sensor.SensorModuleManager()
at ModuleManager Microsoft.Tri.Sensor.SensorService.CreateModuleManager()
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)

 

The install reported that auditing was not configured correctly but according the to guide it is in place (I can see the events in the security log).

 

Any ideas on what I can do to start the service?

6 Replies
best response confirmed by Bjarne Abraham (Occasional Contributor)
Solution

@Bjarne Abraham 
go to the sensor list in MDI portal, click on this new sensor name, and add to the list in the dialog a fully qualified DC name that it can use to resolve AD entities.

once that it should start fine within a few minutes. 

@Eli Ofek I'll check and try later and get back, thanks.

It worked :)
I was not able to see this in the install guide?
At the moment I've added two DC's to the list - it do now have a health issue towards one of them which seems strange as the sensor logs indicate that it's communicating with both DCs in the list?
Everything is good now :) Just had to wait a bit...

Sensor Should be installed on ADFS server and ADFS proxy server or ADFS server is enough?@Eli Ofek 

@Ehab_Communities I think that installing on the ADFS server is sufficient. The ADFS-Proxy is just that, a proxy, it does not do any validation of requests, it only passes them through to the actual ADFS server to process.

Atleast that's how I think it works.