AppFabric Hosting Services Installation Class

  • ID:  Microsoft.ApplicationServer.ServerRole
  • Description:  This class represents the installation of the AppFabric Hosting Services features on a Windows machine.
  • Class Hierarchy: 
    Object
    Configuration Item
    Logical Entity
    Computer Role
    Windows Computer Role
    AppFabric Hosting Services Installation

  • Attributes:  Public, Hosted
Login
This event indicates that the Workflow Management Service failed to execute an instance command. 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. 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. 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. 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. This event indicates that the service could not open an ETW session. Monitoring will not work if this problem occurs. This event indicates that the Event Collection Service’s logon does not have sufficient permissions to perform a required ETW task. This event indicates that the service could not create an ETW session. Monitoring will not work if this problem occurs. 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. 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. 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. This event indicates that the Event Collection Service was unable to read a particular web.config file. This event indicates that the Event Collection Service encountered an exception at runtime while listening to ETW. If this happens, monitoring will not function. 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. This monitor uses SCOM’s built in support for NT service monitoring to make sure the Event Collection Service is running. 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. . This event indicates that the Event Collection Service could not unregister an event source (provider) from an ETW session. This event indicates that the event collection service encountered an unhandled exception that was unexpected. 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. This event indicates that no event collector configuration was found for an Event Collection Service. This configuration should be located in the <Microsoft.ApplicationServer> section of the machine’s root web.config file. The service will fail when this error is encountered and no monitoring will occur. 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> section of the machine’s root web.config file. The service will fail when this error is encountered and no monitoring will occur. 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> section of the machine’s root web.config file. The service will continue to run with the previous configuration. 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. This event indicates that multiple IIS Web Applications have configured monitoring at different levels, but use the same provider Id. 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. 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. This event indicates that the WMS is not able to activate any service hosts for instances stored in the specified instance store. This monitor uses SCOM’s built in support for NT service monitoring to make sure the Workflow Management Service is running. This event indicates that the Workflow Management Service failed to activate a service host because the Service Management Endpoint was not available. This event indicates that the Workflow Management Service failed to activate a service host because the Service Management Endpoint threw an exception. 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. This event indicates that the Workflow Management Service was unable to read a particular web.config file. 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. This event indicates that an instance store was specified in the <Microsoft.ApplicationServer> configuration section, but the “name” attribute did not resolve correctly. 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. 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. This event indicates that an unknown startup argument has been passed to the WMS. 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. 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. This class represents the installation of the AppFabric Hosting Services features on a Windows machine. Defines the basic properties of computers running Windows operating systems This class represents the collection of AppFabric Hosting Services machines in the management group. This class represents a Windows NT Service that AppFabric installs. This service is responsible for collecting event data from WCF and WF services that are managed by AppFabric and sending that data to a monitoring database. This class represents the grouping of all IIS web sites on a machine that contain at least one WCF or WF service that is being managed by AppFabric. This class represents a Windows NT Service that AppFabric installs. This service is responsible providing failover and instance control capabilities to the Workflow Services being managed by AppFabric.

Download diagram as a Visio file

Properties

Display Name Description
Asset Status Asset status
Display Name Display name of the object.
Notes Notes
Object Status Object status
Package Version  
Product Version  

Discovered By

Name Description
AppFabric Hosting Services Seed Discovery This is the seed discovery that discovers AppFabric Hosting Services installations.

Relations

Health Source
NameClassType
Hosting Services Installations Host Event Collection Services AppFabric Hosting Services Installation Hosting
Hosting Services Installations Host IIS Web Sites AppFabric Hosting Services Installation Hosting
Hosting Services Installations Host Workflow Management Services AppFabric Hosting Services Installation Hosting
Owned By User Configuration Item Reference
Affects Customers Configuration Item Reference
Serviced By User Configuration Item Reference
Contains Configuration Item Configuration Item Membership
Is Related to Configuration Item Configuration Item Reference
Config Item References Location Configuration Item Reference
Entity Watched By Perspective Object Reference

Health Target
NameClassType
Hosting Services Nodes Contain Hosting Services Installations AppFabric Hosting Services Installation Membership
Hosts Windows Computer Role Windows Computer Role Hosting

Class Knowledgebase

Summary

This class represents the installation of the AppFabric Hosting Services features on a Windows machine.

External References
This class does not contain any external references.

See Also for Windows Server AppFabric Management Pack


Downloads for Windows Server AppFabric Management Pack