| | DisplayName | Description | ID | Target | Parent Monitor | Category | Enabled | Instance Name | Counter Name | Frequency | Alert Generate | Alert Severity | Alert Priority | Alert Auto Resolve | Monitor Type | Remotable | Accessibility | RunAs |
|---|
 | ETW Session Start State | This event indicates that the service could not create an ETW session. Monitoring will not work if this problem occurs. | Microsoft.ApplicationServer.EventCollector.Event101.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| DB Write State | This event indicates that a particular database connection threw an exception when trying to write events for an application. This will usually be due to a misconfigured connection string, network connectivity issues, or security issues. | Microsoft.ApplicationServer.EventCollector.Event108.TimerReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| ETW Permissions State | This event indicates that the Event Collection Service’s logon does not have sufficient permissions to perform a required ETW task. | Microsoft.ApplicationServer.EventCollector.Event112.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| ETW General Access State | This event indicates that the Event Collection Service could not access the ETW APIs. This usually indicates that an unsupported or invalid Windows installation is present. Monitoring will not work if this problem occurs. | Microsoft.ApplicationServer.EventCollector.Event115.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Unable to process event record | This event indicates that the Event Collection service failed to process an individual event. This should be very rare, but if you see it continuously there may be a problem. . | Microsoft.ApplicationServer.EventCollector.Event120.TimerReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Register Trace Provider State | This event indicates that the Event Collector failed to add a particular event source (provider) to the current session. Monitoring will not work for the application(s) that are a part of this source. | Microsoft.ApplicationServer.EventCollector.Event121.ManualReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Provider in Too Many Sessions State | This event indicates that the Event Collector failed to add a particular event source (provider) to the current session. Monitoring will not work for the application(s) that are a part of this source. | Microsoft.ApplicationServer.EventCollector.Event122.ManualReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DB Connection State | This event indicates that a particular database connection threw an exception when trying to open a connection. This will usually be due to a misconfigured connection string, network connectivity issues, or security issues. | Microsoft.ApplicationServer.EventCollector.Event126.TimerReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Read application config - General failure | This event indicates that the Event Collection Service was unable to read a particular web.config file. | Microsoft.ApplicationServer.EventCollector.Event130.ManualReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| ETW Open Session State | This event indicates that the service could not open an ETW session. Monitoring will not work if this problem occurs. | Microsoft.ApplicationServer.EventCollector.Event134.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Reading event from ETW - General failure | This event indicates that the Event Collection Service encountered an exception at runtime while listening to ETW. If this happens, monitoring will not function. | Microsoft.ApplicationServer.EventCollector.Event135.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Event Destination Known State | This event indicates that an event has been collected, but no database connection has ever been established for the required destination. Since the connection was never established, the system will drop the event as opposed to buffering it and retrying. | Microsoft.ApplicationServer.EventCollector.Event142.TimerReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Unregister Trace Provider State | This event indicates that the Event Collection Service could not unregister an event source (provider) from an ETW session. | Microsoft.ApplicationServer.EventCollector.Event146.ManualReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| DB Buffers Available State | This event indicates that an event has been collected, but the buffers allocated to the destination have been filled. The event will be dropped. This usually occurs when the system is under very high stress. | Microsoft.ApplicationServer.EventCollector.Event150.TimerReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.PerformanceState | PerformanceHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| App Connection String Reference State | This event indicates that a particular IIS web.config file has enabled monitoring, and specifies a connection string reference. However, the referenced connection string could not be found. | Microsoft.ApplicationServer.EventCollector.Event152_153.ManualReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| App Unique Provider Id State | This event indicates that multiple IIS Web Applications have configured monitoring at different levels, but use the same provider Id. | Microsoft.ApplicationServer.EventCollector.Event154.ManualReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.PerformanceState | PerformanceHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Event Delivery State | This event indicates that there was a failure while retrying a write to a monitoring database. The event indicated how many, if any, events were lost due to the failure as well as the number of times a retry has occurred. | Microsoft.ApplicationServer.EventCollector.Event155.TimerReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Bulk Copy Writer Activated State | This event indicates that a bulk copy plugin failed to load properly. These plugins allow the Event Collection Service to optimize its writes to a database. The system will now fall back to using ADO.NET batching which will result in lower performance. | Microsoft.ApplicationServer.EventCollector.Event156.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.PerformanceState | PerformanceHealth | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Event Collection Configuration Found State | This event indicates that no event collector configuration was found for an Event Collection Service. This configuration should be located in the <Microsoft.ApplicationServer><Monitoring> section of the machine’s root web.config file. The service will fail when this error is encountered and no monitoring will occur. | Microsoft.ApplicationServer.EventCollector.Event162.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Event Collection Service Configuration Readable State | This event indicates that there was an exception while trying to read the event collector configuration for an Event Collection Service. This configuration should be located in the <Microsoft.ApplicationServer><Monitoring> section of the machine’s root web.config file. The service will fail when this error is encountered and no monitoring will occur. | Microsoft.ApplicationServer.EventCollector.Event163.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Fresh Configuration State | This event indicates that the event collection service was running successfully, but a configuration change was detected and there was an exception while trying to read the event collector configuration for an Event Collection Service. This configuration should be located in the <Microsoft.ApplicationServer><Monitoring> section of the machine’s root web.config file. The service will continue to run with the previous configuration. | Microsoft.ApplicationServer.EventCollector.Event200.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| App Config Readable State | This event indicates that the event collection service encountered an unhandled exception that was unexpected. | Microsoft.ApplicationServer.EventCollector.Event25001.ManualReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Valid Scope Name State | This event indicates that an invalid command line parameter was passed to the event collection service at startup. This will cause the service to fail and no monitoring will occur. | Microsoft.ApplicationServer.EventCollector.Event50501.AutoReset | Microsoft.ApplicationServer.EventCollectorService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Service Stopped | This monitor uses SCOM’s built in support for NT service monitoring to make sure the Event Collection Service is running. | Microsoft.ApplicationServer.EventCollector.State | Microsoft.ApplicationServer.EventCollectorService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.CheckNTServiceStateMonitorType | True | Public | |
| Operation History Failure Count | The monitoring database logs administrative events in a table called the operations history table. This monitor checks that table for errors and surfaces them. | Microsoft.ApplicationServer.FailedOperationHistoryTableRowCount | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | System.Health.PerformanceState | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.FailedStagingTableRowCount.MonitorType | True | Public | |
| Failed Staging Table Row Count | In the unlikely event that an exception occurs while processing a particular event in the temporary (staging) table, the raw event is deposited into a failed staging table. | Microsoft.ApplicationServer.FailedStagingTableRowCount | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | System.Health.PerformanceState | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.FailedStagingTableRowCount.MonitorType | True | Public | |
| Monitoring Database Available | This monitor periodically checks that a SQL monitoring database is accessible via a SQLConnection. If the database is not accessible then monitoring data might be getting lost on machines that are collecting events. | Microsoft.ApplicationServer.MonitoringStore.State | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | System.Health.AvailabilityState | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.Store.State.MonitorType | True | Public | |
| Instantiated control provider for instance store | This event indicates that a SQL Instance store control provider object failed to initialize. | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50908 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStore.ControlProviderInstantiation | Custom | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Failed to remove command from instance store | This event indicates that the Workflow Management Service executed a command, but failed to remove it from the queue (exception). The service will retry periodically. If the monitor doesn’t see the event for 10 minutes it assumes the problem has been fixed and resets the monitor. | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50911 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceConnection.ProviderCommunication | PerformanceHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Store control provider defined for instance store provider | A control provider is required in order to execute workflow instance commands via the Workflow Management Service. This error indicates that the storeControlProvider attribute in the <Microsoft.ApplicationServer><persistence><instanceStoreProviders> element is missing or empty. You will find this configuration in the machine's root web.config file. | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50912 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStore.ControlProviderInstantiation | Custom | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Store provider defined for instance store provider | This event indicates that an instance store provider has been specified in an IIS web.config file, but no providerName was specified. | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50913 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStoreConnection.InstanceStoreInstantiation | Custom | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Instance Store Instantiated | This event indicates that a SQL Instance store object failed to initialize | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50915 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStoreConnection.InstanceStoreInstantiation | Custom | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Provider definition for instance store found | This event indicates that a Workflow Management Service has been configured to use a SQLInstanceStore, but the store’s definition could not be found in an IIS web.config file. | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50929 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStoreConnection.InstanceStoreInstantiation | Custom | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Recycling owner of instance store | This event indicates that an instance store provider threw an exception and the Workflow Management Service will initialize a new instance of the provider. | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50930.TimerReset | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStoreConnection.StoreCommunication | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Recycling owner of instance store because store cancelled operation | This event indicates that an instance store returned an 'Operation Cancelled' exception | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50932.TimerReset | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStoreConnection.StoreCommunication | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Failed to obtain command from instance store | This event indicates that the Workflow Management Service failed to retrieve a command from the queue (exception). The service will retry periodically. If the monitor doesn’t see the event for 10 minutes it assumes the problem has been fixed and resets the monitor. | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50939 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceConnection.ProviderCommunication | PerformanceHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Instance store specifies an unknown instance store provider. | | Microsoft.ApplicationServer.PersistenceStoreConnection.Event50945 | Microsoft.ApplicationServer.PersistenceStoreConnection | Microsoft.ApplicationServer.PersistenceStoreConnection.InstanceStoreInstantiation | ConfigurationHealth | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| SQL Instance Store Co-Location | This monitor checks to see if a SQL Instance Store is installed in the same database as the monitoring database artifacts. | Microsoft.ApplicationServer.PersistenceStoreExists | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | System.Health.PerformanceState | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.PersistenceStoreExists.MonitorType | True | Public | |
| Staging Table Row Count | The AppFabric SQL monitoring database stores events in a temporary table and then periodically imports them into tables that are visible to external tools such as IIS Manager. If that table grows too large, it is most likely that your applications are emitting events at a rate that is faster than the import procedure can move them. | Microsoft.ApplicationServer.StagingTableRowCount | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | System.Health.PerformanceState | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.StagingTableRowCount.MonitorType | True | Public | |
| Staging Table Transfer Events Job | There is a job that runs periodically to import monitoring events from the temporary (staging) table into the tables that are consumable by tools such as IIS Manager. This monitor checks to make sure that job runs periodically and goes “Red” if it has not been run recently. This indicates that the data visible to the tools is not up to date. | Microsoft.ApplicationServer.StagingTableTransferEventsJob | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | Microsoft.ApplicationServer.StagingTableJobStatus | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.StagingTableJobStatus.MonitorType | True | Public | |
| Staging Table WCF Events Job | There is a job that runs periodically to import monitoring events from the temporary (staging) table into the tables that are consumable by tools such as IIS Manager. This monitor checks to make sure that job runs periodically and goes “Red” if it has not been run recently. This indicates that the data visible to the tools is not up to date. | Microsoft.ApplicationServer.StagingTableWcfEventsJob | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | Microsoft.ApplicationServer.StagingTableJobStatus | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.StagingTableJobStatus.MonitorType | True | Public | |
| Staging Table WF Events job | There is a job that runs periodically to import monitoring events from the temporary (staging) table into the tables that are consumable by tools such as IIS Manager. This monitor checks to make sure that job runs periodically and goes “Red” if it has not been run recently. This indicates that the data visible to the tools is not up to date. | Microsoft.ApplicationServer.StagingTableWfEventsJob | Microsoft.ApplicationServer.MonitoringStoreConnectedConnection | Microsoft.ApplicationServer.StagingTableJobStatus | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.StagingTableJobStatus.MonitorType | True | Public | |
| Web Application Monitoring Enabled State | This monitor checks to see that monitoring is enabled for an application. If monitoring is not enabled, then the other monitors that target web services will not function. | Microsoft.ApplicationServer.WebApplication.Monitoring.State | Microsoft.ApplicationServer.WebApplication | System.Health.ConfigurationState | Custom | True | | | 0 | False | | | True | Microsoft.ApplicationServer.Monitoring.State.MonitorType | True | Public | |
| Average Call Duration | This monitor will periodically determine a web service’s average call duration (in ms) by checking the monitoring database. | Microsoft.ApplicationServer.WebService.AverageCallDuration | Microsoft.ApplicationServer.WebService | System.Health.PerformanceState | Custom | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.ApplicationServer.WebServer.ThreeState.MonitorType | True | Public | |
| Operation Call Rate | This monitor will periodically determine a web service’s average call rate (in calls per second) by checking the monitoring database. | Microsoft.ApplicationServer.WebService.AverageThroughput | Microsoft.ApplicationServer.WebService | System.Health.PerformanceState | Custom | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.ApplicationServer.WebServer.ThreeState.MonitorType | True | Public | |
| Operation Failure Rate | This monitor will periodically determine a web service’s call failure rate (in exceptions per hour) by checking the monitoring database. A call is considered to have failed if it throws an unhandled exception from within the operation’s implementation. | Microsoft.ApplicationServer.WebService.CallFailureRate | Microsoft.ApplicationServer.WebService | System.Health.PerformanceState | Custom | True | | | 0 | True | MatchMonitorHealth | Normal | True | Microsoft.ApplicationServer.WebServer.ThreeState.MonitorType | True | Public | |
| Unhandled exceptions | This event indicates that an unexpected unhandled exception has occurred in the Workflow Management Service. You will need to examine the details in the event to see what went wrong. | Microsoft.ApplicationServer.WMS.Event25001 | Microsoft.ApplicationServer.WFManagementService | System.Health.AvailabilityState | Custom | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Configuration Error | This event indicates that the Workflow Management Service was unable to read a particular web.config file. | Microsoft.ApplicationServer.WMS.Event50902 | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| net.pipe protocol is not activated | This event indicates that a particular web site or application does not have the net.pipe protocol enabled. This protocol is required for the Workflow Management to communicate with service hosts. | Microsoft.ApplicationServer.WMS.Event50919.ManualReset | Microsoft.ApplicationServer.WFManagementService | Microsoft.ApplicationServer.WFManagementService.ExecutionOfCommands | AvailabilityHealth | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Service management service activated service | This event indicates that the Workflow Management Service failed to activate a service host because the Service Management Endpoint threw an exception. | Microsoft.ApplicationServer.WMS.Event50923.TimerReset | Microsoft.ApplicationServer.WFManagementService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Invoke service management service | This event indicates that the Workflow Management Service failed to activate a service host because the Service Management Endpoint was not available. | Microsoft.ApplicationServer.WMS.Event50928.TimerReset | Microsoft.ApplicationServer.WFManagementService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Activated service hosts for instances stored in instance store | This event indicates that the WMS is not able to activate any service hosts for instances stored in the specified instance store. | Microsoft.ApplicationServer.WMS.Event50934.TimerReset | Microsoft.ApplicationServer.WFManagementService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| WMS Configuration found for specific WMS service | This event indicates that a named WMS instance’s configuration could not be loaded. This configuration should exist in the machine’s root IIS web.config file’s <Microsoft.ApplicationServer> section. | Microsoft.ApplicationServer.WMS.Event50936 | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | Custom | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| WMS Service Configuration Found | This event indicates that the WMS configuration could not be loaded. This configuration should exist in the machine’s root IIS web.config file’s <Microsoft.ApplicationServer> section. | Microsoft.ApplicationServer.WMS.Event50937 | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | Custom | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Error in configuration section. Location not found. | This event indicates that an instance store was specified in the <Microsoft.ApplicationServer> configuration section, but the “location” attribute did not resolve to a valid web.config location. | Microsoft.ApplicationServer.WMS.Event50942 | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Error in configuration section. Instance store name not defined at location. | This event indicates that an instance store was specified in the <Microsoft.ApplicationServer> configuration section, but the “name” attribute did not resolve correctly. | Microsoft.ApplicationServer.WMS.Event50943 | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | True | Warning | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Service did not find any instance stores. | This event indicates that no stores are defined in any web.config on the machine. This means that the Workflow Management Service is running, but is not doing any work. | Microsoft.ApplicationServer.WMS.Event50944 | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Unknown Argument Supplied | This event indicates that an unknown startup argument has been passed to the WMS. | Microsoft.ApplicationServer.WMS.Event50946.ManualReset | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | ConfigurationHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | True | Public | |
| Empty command line value for Name | This event indicates that a blank value was passed as the “-name” argument to the Workflow Management Service when it started. This will prevent the service from starting. | Microsoft.ApplicationServer.WMS.Event50947 | Microsoft.ApplicationServer.WFManagementService | System.Health.ConfigurationState | PerformanceHealth | True | | | 0 | True | Error | Normal | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Controlled instance from end point | This event indicates that the Workflow Management Service failed to execute an instance command. | Microsoft.ApplicationServer.WMS.Event910.TimerReset | Microsoft.ApplicationServer.WFManagementService | Microsoft.ApplicationServer.WFManagementService.ExecutionOfCommands | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| AppFabric Workflow Management Service State | This monitor uses SCOM’s built in support for NT service monitoring to make sure the Workflow Management Service is running. | Microsoft.ApplicationServer.WorkflowMangementService.State | Microsoft.ApplicationServer.WFManagementService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.CheckNTServiceStateMonitorType | True | Public | |
| HA Enabled Secondary Node Down | This monitor checks to make sure a secondary node is available for named caches that have high availability mode enabled. | Microsoft.DistributedCache.Cache.HAEnabledSecondaryNodeDown | Microsoft.DistributedCache.Cache | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.DistributedCache.HAEnabledSecondaryNodeDown.MonitorType | True | Public | |
| Named Cache Not Accessible | This monitor checks to make sure named caches are available. | Microsoft.DistributedCache.Cache.NamedCacheNotAccessible | Microsoft.DistributedCache.Cache | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.DistributedCache.NamedCacheNotAccessible.MonitorType | True | Public | |
| Distributed Cache Host Crashes | This event indicates that the cache host has crashed unexpectedly due to an unhandled exception. | Microsoft.DistributedCache.CacheHostService.Event110.AutoReset | Microsoft.DistributedCache.CacheHostService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.2SingleEventLog2StateMonitorType | True | Public | |
| Cache Host Service Memory Evicted | This monitor looks at the Objects Evicted performance counter. | Microsoft.DistributedCache.CacheHostService.MemoryEvicted | Microsoft.DistributedCache.CacheHostService | System.Health.PerformanceState | PerformanceHealth | False | | | 0 | False | | | True | Microsoft.DistributedCache.Host.Eviction.MonitorType | True | Public | |
| Cache Host Service Objects Evicted | This monitor looks at the Objects Evicted performance counter. | Microsoft.DistributedCache.CacheHostService.ObjectsEvicted | Microsoft.DistributedCache.CacheHostService | System.Health.PerformanceState | PerformanceHealth | False | | | 0 | False | | | True | Microsoft.DistributedCache.Host.Eviction.MonitorType | True | Public | |
| Cache Host Service Objects Expired | This monitor looks at the Objects Expired performance counter. | Microsoft.DistributedCache.CacheHostService.ObjectsExpired | Microsoft.DistributedCache.CacheHostService | System.Health.PerformanceState | PerformanceHealth | False | | | 0 | False | | | True | Microsoft.DistributedCache.Host.Eviction.MonitorType | True | Public | |
| Cache Host Service State | This monitor uses SCOM’s built in support for NT service monitoring to make sure the Cache Host Service is running. | Microsoft.DistributedCache.CacheHostService.State | Microsoft.DistributedCache.CacheHostService | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | False | | | True | Microsoft.Windows.CheckNTServiceStateMonitorType | True | Public | |
| Cluster Config Store State | This monitor uses PowerShell to test the connection to the cache config store, and additionally checks to see if the configuration is valid.
If this fails, the cache service will not be able to retrieve its configuration and caching will not function properly. | Microsoft.DistributedCache.Cluster.ConfigStore.State | Microsoft.DistributedCache.CacheAdmin | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.DistributedCache.Cluster.TwoState.MonitorType | True | Public | |
| Cluster Config Store Node State | This monitor uses either a SQLConnection or a remote file read to test the availability of the node that is hosting the cache configuration.
If this fails, the cache service will not be able to retrieve its configuration and caching will not function properly. | Microsoft.DistributedCache.Cluster.ConfigStoreNode.State | Microsoft.DistributedCache.CacheAdmin | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.DistributedCache.Cluster.ConfigNodeState.MonitorType | True | Public | |
| Cluster Lead Host State | This monitor ensures that at least one lead host is available in the cluster. If this fails, then the cluster’s functionality will become degraded. | Microsoft.DistributedCache.Cluster.LeadHost.State | Microsoft.DistributedCache.CacheAdmin | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.DistributedCache.Cluster.ThreeState.MonitorType | True | Public | |
| Cluster State | This monitor ensures that at least one host is available in the cluster. If this fails, then the cluster will become unavailable. | Microsoft.DistributedCache.Cluster.State | Microsoft.DistributedCache.CacheAdmin | System.Health.AvailabilityState | AvailabilityHealth | True | | | 0 | True | Error | Normal | True | Microsoft.DistributedCache.Cluster.TwoState.MonitorType | True | Public | |
Home