OWA Farm is configured on two 2012 servers. Lync 2013 installed on server 2012 as well.
I can access all services, internally and externally without issues on the client end.
However, my OWA farm machines are marked as Unhealthy per get-OfficeWebAppMachines.
The OWA Farm system Logs show multiple events related to source Office Web Apps Monitoring, event ID(s) 1004, 1010, 2004, & 2010.
What are the BroadcastServicesWatchdog_Wfe & AgentManagerWatchdog that are running, reporting these event codes, and where can it be managed?
The actual event codes
1004:
<?xml version="1.0" encoding="utf-16"?>
<HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<HealthMessage>AgentManagerWatchdog reported status for AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage>
</HealthReport>
1010:
<?xml version="1.0" encoding="utf-16"?>
<HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<HealthMessage>BroadcastServicesWatchdog_Wfe reported status for BroadcastServices_Host in category '3'. Reported status: Contacting Participant.svc failed with an exception: The remote server returned an error: (404) Not Found.</HealthMessage>
</HealthReport>
2004:
<?xml version="1.0" encoding="utf-16"?>
<HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<HealthMessage>AgentManagerWatchdog reported status for AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage>
</HealthReport>
2010:
<?xml version="1.0" encoding="utf-16"?><HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<HealthMessage>BroadcastServicesWatchdog_Wfe reported status for BroadcastServices_Host in category '3'. Reported status: Contacting Participant.svc failed with an exception: The remote server returned an error: (404) Not Found.</HealthMessage>
</HealthReport>