Forum Discussion
Cannot get ATP sensors to Start
Hi, I am able to successfully install the ATP's sensors on my DC's, but cannot get the Service to Start. I have created a gMSA account and opened up the firewall, but am getting Events 7000, 7031, and 7038.
The AATPSensor service was unable to log on as xxxxxxxxxx\gMSAcct01$ with the currently configured password due to the following error:
The user name or password is incorrect.
To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).
Seth Holek uninstall and reinstall to make sure the service is deployed correctly, this is broken because you changed the services logon... it is unable to retrieve the gmsa password this way,
the gmsa should only be configured on the portal, the system takes care of all the rest...
12 Replies
- EliOfek
Microsoft
Seth Holek , you should find the clues in the sensor's own logs folder, not in the windows event log.
Just to be clear, the gmsa account was configured in the portal right? you didn't change the actual windows service, did you ? the sensor should run with it's pre configured virtual account (which inherits local service)
Yes, I added the gmsa account to the Directory Services credentials in the Portal, and I did change the service from Local Service to the gmsa account.
Here are errors from the ATP logs:
2020-06-29 14:20:40.9680 Error DirectoryServicesClient+<CreateLdapConnectionAsync>d__38 Microsoft.Tri.Infrastructure.ExtendedException: CreateLdapConnectionAsync failed [DomainControllerDnsName=SIT-DC12.xxxxxxxx.local]
at async Task<LdapConnection> Microsoft.Tri.Sensor.DirectoryServicesClient.CreateLdapConnectionAsync(DomainControllerConnectionData domainControllerConnectionData, bool isGlobalCatalog, bool isTraversing)
at async Task<bool> Microsoft.Tri.Sensor.DirectoryServicesClient.TryCreateLdapConnectionAsync(DomainControllerConnectionData domainControllerConnectionData, bool isGlobalCatalog, bool isTraversing)2020-06-29 14:20:39.8430 Warn DirectoryServicesClient CreateLdapConnectionAsync failed to retrieve group managed service account password. [DomainControllerDnsName=SIT-DC12.xxxxxxx.local Domain=xxxxxxxx.local UserName=gMSAcct01$ ]
2020-06-29 14:20:40.9680 Error DirectoryServicesClient+<CreateLdapConnectionAsync>d__38 Microsoft.Tri.Infrastructure.ExtendedException: CreateLdapConnectionAsync failed [DomainControllerDnsName=SIT-DC12.xxxxxxxx.local]
at async Task<LdapConnection> Microsoft.Tri.Sensor.DirectoryServicesClient.CreateLdapConnectionAsync(DomainControllerConnectionData domainControllerConnectionData, bool isGlobalCatalog, bool isTraversing)
at async Task<bool> Microsoft.Tri.Sensor.DirectoryServicesClient.TryCreateLdapConnectionAsync(DomainControllerConnectionData domainControllerConnectionData, bool isGlobalCatalog, bool isTraversing)
2020-06-29 14:20:41.0305 Error DirectoryServicesClient Microsoft.Tri.Infrastructure.ExtendedException: Failed to communicate with configured domain controllers
at new Microsoft.Tri.Sensor.DirectoryServicesClient(IConfigurationManager configurationManager, IDomainNetworkCredentialsManager domainNetworkCredentialsManager, IImpersonationManager impersonationManager, IMetricManager metricManager, IWorkspaceApplicationSensorApiJsonProxy workspaceApplicationSensorApiJsonProxy)
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)- EliOfek
Seth Holek uninstall and reinstall to make sure the service is deployed correctly, this is broken because you changed the services logon... it is unable to retrieve the gmsa password this way,
the gmsa should only be configured on the portal, the system takes care of all the rest...
