0

We have been having servers just stop responding and we have to do a hard reset on them. We have been searching for a cause and solution to this issue, as it appears to be happening more frequently.

The servers are Azure VM's running 2019 Datacenter. They experience an eventID of 21402 followed by eventID 21414. I am somewhat thinking that the machine is not responding after the first time the error is thrown, but it gets noticed fairly quickly and we have it restarting after a few minutes so these events occur a few times before it is restarted.

eventID 21402

Forced to terminate the following process started at 2:38:52 AM because it ran past the configured timeout 60 seconds.

Command executed: "C:\windows\system32\cscript.exe" /nologo "MonitorKnowledgeDiscovery.vbs" Working Directory: C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 6\24\

One or more workflows were affected by this.

Followed by the 21414 event:

Data was found in the output, but has been dropped because the Event Policy for the process started at 2:38:52 AM has detected errors. The 'ExitCode' policy expression: [^0]+ matched the following output: 3

The same command and directory are listed in the second event too.

Has anyone run across this? or might have an idea on how to move forward with this?

Thank you

0 Answers0