Server stopped reporting to ePO

[User68214094]

I have had 2 servers stop reporting to the ePO in the past 4 days. Does anyone know anything about this? I have attached 2 screenshots from error logs. I have also opened a service ticket.

[cdinet]

What version of the agent are you running?  If the service is crashing, make sure you are at a later version of agent, as there were some crashes fixed in some later versions.  Otherwise, we would need a process dump (procdum -ma -t masvc.exe) and corresponding mer for same time dump was obtained.

In order to get a process dump, you will probably need to disable self protection in the agent policy.  Does it fail to connect consistently or can it connect intermittently to get a policy change?  How frequently is it crashing?  Do you notice that it crashes during an update, policy enforcement, or other functionality?

[User68214094]

2 different servers have failed one time and failed to reconnect, we were able to correct it manually. One occurred Monday and 1 occurred last night. Other than that they seem to be running fine. I have downloaded masvc logs and don't see a major issue.

[cdinet]

When the system fails to connect, get the masvc log and look for the connection attempt and what the errors were.  There are 2 basic types of failures, but each has many reasons.  

1. agent reaches epo but epo or something in between rejects communication for one reason or another.  Could be the agent sends bad data, or some issue on epo server or agent handler where it can't respond properly

2.  agent never reaches epo or ah at all - possible firewall/proxy/ssl inspection, network issue, dns, etc.