SOLVED

Cannot get ADFS ATP Sensor service to start

%3CLINGO-SUB%20id%3D%22lingo-sub-2221111%22%20slang%3D%22en-US%22%3ECannot%20get%20ADFS%20ATP%20Sensor%20service%20to%20start%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221111%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20sensors%20installed%20and%20working%20on%20both%20of%20my%20domain%20controllers%20(Server%202016)%2C%20however%2C%20when%20I%20install%20the%20ADFS%20sensor%20on%20my%20ADFS%20server%20(also%202016)%20the%20service%20refuses%20to%20start.%20I%20get%20the%20following%20error.%20I%20have%20tried%20everything%20I%20can%20conceive%2C%20including%20deleting%20the%20instance%20and%20starting%20over%2C%20trying%20different%20accounts%2Fcredentials%2Fformats%20(both%20the%20single%20label%20domain%20vs.%20the%20.com%20suffix%20format)%20to%20no%20avail.%20The%20error%20is%20as%20follows%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2021-03-18%2020%3A22%3A05.6369%20Error%20DomainNetworkCredentialsManager%20Microsoft.Tri.Infrastructure.ExtendedException%3A%20DomainControllerDnsNames%20is%20empty%20or%20not%20configured%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%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20is%20greatly%20appreciated!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2221396%22%20slang%3D%22en-US%22%3ERe%3A%20Cannot%20get%20ADFS%20ATP%20Sensor%20service%20to%20start%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221396%22%20slang%3D%22en-US%22%3EGo%20to%20the%20sensors%20tab%20in%20the%20MDI%20portal%2C%20click%20on%20the%20registered%20ADFS%20sensor%2C%20and%20add%20to%20the%20list%20a%20fully%20qualified%20DC%20name%20this%20sensor%20can%20contact%20to%20resolve%20AD%20entities.%20once%20you%20do%20that%20and%20press%20sav%2C%20within%2010%20min%20the%20sensor%20should%20overcome%20this%20error.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2221416%22%20slang%3D%22en-US%22%3ERe%3A%20Cannot%20get%20ADFS%20ATP%20Sensor%20service%20to%20start%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221416%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%3BThis%20resolved%20the%20issue!%20Thank%20you%20so%20much%20-%20I%20couldn't%20find%20anything%20online%20to%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I have the sensors installed and working on both of my domain controllers (Server 2016), however, when I install the ADFS sensor on my ADFS server (also 2016) the service refuses to start. I get the following error. I have tried everything I can conceive, including deleting the instance and starting over, trying different accounts/credentials/formats (both the single label domain vs. the .com suffix format) to no avail. The error is as follows:

 

2021-03-18 20:22:05.6369 Error DomainNetworkCredentialsManager Microsoft.Tri.Infrastructure.ExtendedException: DomainControllerDnsNames is empty or not configured
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)

 

Any help is greatly appreciated!

 

 

2 Replies
best response confirmed by amayo21 (New Contributor)
Solution
Go to the sensors tab in the MDI portal, click on the registered ADFS sensor, and add to the list a fully qualified DC name this sensor can contact to resolve AD entities. once you do that and press sav, within 10 min the sensor should overcome this error.

@Eli Ofek This resolved the issue! Thank you so much - I couldn't find anything online to help!

www.000webhost.com