Forum Discussion
Azure ATP sensor update and communication error
Michele D'Angelantonio 2.107 will be deployed in the coming days.
So just so I understand it better - it's not always crashing, but from time to time it crashes, and when it does, it's with this error?
How many total failures since first installed?
I would advise to open a support ticket for this.
Since we haven't seen it before, we will need to collect more data to analyze.
Also, another thing you can try , is that if you currently work with the default winpcap driver, you can replace it with npcap and see if it resolves the issue.
See this for instructions:
you can follow it even of not using nic teaming.
Just make sure to use version
https://nmap.org/npcap/dist/npcap-0.9984.exeAs we currently have compatibility issues with the newer version which we haven't fixed yet.
MicrosoftDid this sensor ever worked, or did it stopped working at some point?
is the message "CaptureFrames exception, exiting" logged after every start crash ?
Di dyou recently installed any product that is using winpcap or npcap on the same machine?
EliOfek thanks for your attention.
The sensor worked on all DCs for some months. I have the first error on january (sensors installed on june).
Nothing is changed on the DCs, the sowtware installed are:
for OfficeSscan we did not use the firewall. So I don't think there is something using npcap or winpcap.
the message "CaptureFrames exception, exiting" is logged on every crash (on my log I have only the last two) but not at the exact time.
thanks again
Mike
- EliOfek
Michele D'Angelantonio was there any recent change to the network stack?
nics removed/added ? drivers changed?
is this a VM or a physical machine?
hi EliOfek
I verified again every log and I found the event ID 7031 with the sensor restart even on june.
the exact error I coan find on the log is:
2020-01-30 02:17:01.9748 Error FrameReader`1 CaptureFrames exception, exiting
Microsoft.Tri.Sensor.FrameReaderException: Failed reading frame [resultCode=-1 message=read error: PacketReceivePacket failed]
at bool Microsoft.Tri.Sensor.FrameReader<TCaptureDevice>.TryReadFrame(out DateTime time, out BufferSlice bufferSlice)
at bool Microsoft.Tri.Sensor.NetworkListener.ParseFrame(FrameReader frameReader)
at void Microsoft.Tri.Sensor.NetworkListener.CaptureFrames(LiveFrameReader[] liveFrameReaders)Two DCs are VM on Hyper-V cluster, the third is on Azure. No network changes.
The issue seems to happen completly randomly.
My first impression was that the issue could be connected to the sensor updates but I've no evidence of that.
I've seen that the new version of the sensor is available from the Jan 26th but no DCs are updated (the ATP portal marks all three DCs as up to date, with version 2.106.7618).
