Application Server: The Event Collection service should be started

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Application Server Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

Issue

The AppFabric Event Collection service has not been started.

Impact

AppFabric monitoring events will not be stored in the monitoring database if the Event Collection service is not running.

The AppFabric role service of the Application Server role uses the Event Collection service that is installed with the AppFabric hosting features to implement monitoring. The Event Collection service reads events from the Event Tracing for Windows (ETW) session and writes them to the monitoring database. An instance of the Event Collection service must run on every computer that hosts the WF and WCF services that you want to monitor.

A default instance of the Event Collection service is installed and configured with the AppFabric installation. For more information about the configuration of the service, see Configure the Event Collection Service (https://go.microsoft.com/fwlink/?LinkId=200786).

Resolution

Start the AppFabric Event Collection service.

To start the Event Collection Service

1. Open a command line running as an administrator, and then execute Net Start “AppFabric Event Collection Service”; or open a PowerShell console, and then execute Start-Service “AppFabric Event Collection Service”.

Additional references

Event Collection Service (https://go.microsoft.com/fwlink/?LinkId=200928)