21000
ExtMon: Service [%1] SID was not found. This sevice cannot register for external monitoring.
21001
ExtMon: Failed to open the external monitoring IPC port (name=[%1]). Trying again with a different unique name.
21005
ExtMon: The request to end the process (ProcessPid=[%1], ProcessName=[%2]) is denied because the process name does not match the process id.
21006
ExtMon: Cannot update the status for service [%1] without the service being registered.
21007
ExtMon: The service registration parameters (ServiceName: [%1] ProcessName: [%2] ProcessID: [%3]) are not valid. Either this is a non-dependant service or there is a process ID or Name mismatch.
21008
ExtMon: The service health report (ServiceName: [%1] ProcessID: [%2]) is not valid. Service Name and Process Id are mismatched.
21010
ExtMon: Monitored service [%1] (Process name: [%2], PID=[%3]) failed to report a healthy status in the required time (Status Interval: [%4]).
21011
ExtMon: Monitored service [%1] (Process name: [%2], PID=[%3]) has updated its status to: NOT healthy.
21012
ExtMon: Monitored service [%1] failed to report a healthy status in the required time. Attempting to end its process with last known PID=[%2].
21013
ExtMon: Updating service [%1] with a new pid=[%2]. The procees id has changed, ensure the service has restarted.
Cause—The Watch dog service identified the Microsoft Forefront UAG DNS64 Service but cannot add its SID. This warning can occur when activating Forefront UAG, or when starting the Microsoft Forefront UAG Watch Dog Service.
Solution—Reinstall Forefront UAG. This message can be ignored and may also be accompanied by Event ID 21507.
Cause—When the Microsoft Forefront UAG DNS64 Service is started it send verification parameters to the Microsoft Forefront UAG Watch Dog Service. If one of the parameters is not verified successfully, an Event ID appears. When these Event IDs appear, DNS64 is still functional and the Microsoft Forefront UAG Watch Dog Service continues to request the relevant parameters. This problem is normally self-correcting.
Cause—Periodically, the Microsoft Forefront UAG DNS64 Service sends a heartbeat to the Microsoft Forefront UAG Watch Dog Service announcing that is up and running. When one of these periodic heartbeats is not sent, the Microsoft Forefront UAG Watch Dog Service sends Event ID 21010 to the Event Viewer. Once several consecutive heartbeats have not been received by the Microsoft Forefront UAG Watch Dog Service, event 2012 is sent to the Event Viewer and the Microsoft Forefront UAG DNS64 Service is restarted.
Cause—The DNS64 service identifies that it has a problem, informs the Microsoft Forefront UAG Watch Dog Service, and the Microsoft Forefront UAG DNS64 Service restarts automatically.
Cause—If the Microsoft Forefront UAG DNS64 Service is stopped in a non-standard way, or fails to unregister when stopped. Event 21013 appears when the Microsoft Forefront UAG DNS64 Service restarts automatically.