Forum Discussion

Tony escamilla's avatar
Tony escamilla
Copper Contributor
Nov 22, 2019

ATP sensor on Server 2016 DC crashing.

Currently we went through  a process of upgrading our DCs to 2016 after doing this and going through process of installing ATP sensor on the servers we are having the service crash or stay in a starting state. 

 

I get the following errors as well.

 

Application log

Event ID 1008

The Open Procedure for service "WmiApRpl" in DLL "C:\Windows\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

 

The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

 

Event ID 2004

Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.

 

System Log

Event ID 7032

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Azure Advanced Threat Protection Sensor service, but this action failed with the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

 

Event Id 7031

The Azure Advanced Threat Protection Sensor service terminated unexpectedly. It has done this 385 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

 

 

I can't seem to find anything regarding this or if I am missing something.  The prereq doesn't seem to show anything special missing so i am stumped.   Any help is welcome.

 

 

Thanks,

 

 

 

10 Replies

  • jomalin's avatar
    jomalin
    Copper Contributor

    I have had this issue pop up recently. Lots of 1008 errors and the ATP sensor wouldn't start and would error in the ATP portal for no communication. Server 2012R2

     

    1008, Perflib

    The Open Procedure for service "WmiApRpl" in DLL "C:\Windows\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

     

    The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

     

    The Open Procedure for service ".NETFramework" in DLL "C:\Windows\system32\mscoree.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

     

    Looking in the log located at "C:\Program Files\Azure Advanced Threat Protection Sensor\2.105.7563.11519\Logs\Microsoft.Tri.Sensor.log" I see this error

     

    2020-01-22 12:31:49.1675 Warn PcapLibraryHelper Verify [Packet.dll-ProductName=WinPcap Packet.dll-ProductVersion=4.1.0.2980 wpcap.dll-ProductName=WinPcap wpcap.dll-ProductVersion=4.1.0.2980]
    2020-01-22 12:31:49.4018 Error WinPcapDeviceList SharpPcap.PcapException: No interfaces found! Make sure libpcap/WinPcap is properly installed on the local machine.
    at List<WinPcapDevice> SharpPcap.WinPcap.WinPcapDeviceList.Devices(string rpcapString, RemoteAuthentication remoteAuthentication)
    at void SharpPcap.WinPcap.WinPcapDeviceList.Refresh()
    at WinPcapDeviceList SharpPcap.WinPcap.WinPcapDeviceList.get_Instance()
    at new Microsoft.Tri.Sensor.NetworkListener(IBufferPool bufferPool, IConfigurationManager configurationManager, IMetricManager metricManager, INetworkAdaptersManager networkAdaptersManager, IParsingOrchestrator parsingOrchestrator, 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)

     

     

    I downloaded and installed npcap, restarted the sensor and everything cleared up. 

     

    Is there an issue with the ATP sensors install of WinPcap?

    • EliOfek's avatar
      EliOfek
      Icon for Microsoft rankMicrosoft

      jomalin , the sensor should work fine with both most of the time.

      Currently the default is winpcap, and if you require nic teaming support then we need npcap,

      but you can work with npcap just fine even without teaming.

      We are also considering at some point to make npcap the default and not winpcap.

       

      As to why winpcap did not work for your case, it's hard to tell, usually it means there is another product installed that is also using winpcap but with a configuration we do not support.

      If you would like to research it a support call might be in order, but if npcap just work for you, I guess that would be a waste of your time...

       

      Eli

      • Tony escamilla's avatar
        Tony escamilla
        Copper Contributor

        EliOfek 

         

        I actually get the same errors as jomalin but with one exception on these servers and it is mixture as some are 2012 R2 and others are 2016.  I also never have installed WinPcap.  I wasn't planning on installing npcap either as it doesn't look like it requires it unless i have a physical server and require NIC teaming. In my case all the servers (4) are running on VMware so the only requirement is the change on the NIC adapter being used.  As for npcap it seems that my installs work fine until the update process goes out and looks for updates and that is where all hell breaks loose.  the ATP sensor process stops and then never comes back on.  NpCap then gets installed which it seems is coming from the sensor but I have not been able to trace where that install is coming from.  What makes it even more weird is that it is only affecting 4 out of the more than 10 DCs we have in our environment.  Should I install Winncap to see if all works fine then. I do have a support ticket opened with support but we are just stumped as to why npcap is just being installed on these and not the rest. 

Resources