Forum Discussion
manojviduranga
Feb 28, 2023Iron Contributor
ATP Sensor service is continuously trying to start but stops itself
Hello Techies,
I've installed ATP Sensor across multiple DCs and it was completed successfully. However, the service is continuously trying to start and stop itself on every machine it's been installed on, with the following error message appearing in the Microsoft.Tri.Sensor-Errors log:
Error ExceptionHandler Microsoft.Tri.Infrastructure.ExtendedException: RestrictCpuAsync failed, exiting ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
at Stream System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, out TransportContext context)
at void System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at async Task<HttpResponseMessage> System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task<HttpResponseMessage> sendTask, HttpRequestMessage request, CancellationTokenSource cts, bool disposeCts)
at async Task<TResponse> Microsoft.Tri.Common.CommunicationWebClient.SendAsync<TResponse>(byte[] requestBytes, int offset, int count)
at async Task<TResponse> Microsoft.Tri.Common.CommunicationWebClient.SendWithRetryAsync<TResponse>(byte[] requestBytes, int offset, int count)
at async Task Microsoft.Tri.Common.CommunicationWebClient.SendAsync(IVoidRequest request)
at async Task Microsoft.Tri.Sensor.Common.ServiceProxy<TWebClientConfiguration>.SendAsync(IVoidRequest request)
at async Task Microsoft.Tri.Sensor.SensorResourceManager.RestrictCpuAsync()
--- End of inner exception stack trace ---
Has anyone came across this issue? Really appreciate any pointers here.
Thank you!
- The resolution was to add the following change in the registry of each DC.
Changed the following value from "1" to "0"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentCOntrolSet\Control\SecurityProviders\SCHANNEL]
"DisableRenegoONserver"=dword:00000001
- manojvidurangaIron ContributorThe resolution was to add the following change in the registry of each DC.
Changed the following value from "1" to "0"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentCOntrolSet\Control\SecurityProviders\SCHANNEL]
"DisableRenegoONserver"=dword:00000001- Jacampbell
Microsoft
manojviduranga - what is that key is missing. - we do not see
"DisableRenegoONserver"=dword:00000001
- Karim HamdyCopper Contributordo you have proxy in between ?
- manojvidurangaIron Contributor
1. Service endpoint is reachable from the servers
2. Application based firewall filtering the internet access. The required rules have been added, but for testing we have also granted access to all internet, no filtering, no SSL inspection but the same error occurs. Packet captures show no errors.
3. Root certificates are all green
4. Restarted the servers. No change- EliOfek
Microsoft
This is not related to internet access.
Read my previous message again...
- EliOfek
Microsoft
check the updater log for any errors at the same time.
If not, check why communication is blocked between the sensor process and the updater process via TCP localhost:444