7 Appendix B: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

 The terms "earlier" and "later", when used with a product version, refer to either all preceding versions or all subsequent versions, respectively. The term "through" refers to the inclusive range of versions. Applicable Microsoft products are listed chronologically in this section.

Windows Client

  • Windows 2000 Professional operating system

  • Windows XP operating system

  • Windows Vista operating system

  • Windows 7 operating system

  • Windows 8 operating system

  • Windows 8.1 operating system

  • Windows 10 operating system

  • Windows 11 operating system

Windows Server

  • Windows 2000 Server operating system

  • Windows Server 2003 operating system

  • Windows Server 2008 operating system

  • Windows Server 2008 R2 operating system

  • Windows Server 2012 operating system

  • Windows Server 2012 R2 operating system

  • Windows Server 2016 operating system

  • Windows Server operating system

  • Windows Server 2019 operating system

  • Windows Server 2022 operating system

  • Windows Server 2025 operating system 

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.2: Windows collects method call statistics in 1-second intervals and calculates the statistics over the four most recent intervals.

<2> Section 2.2.4: On Windows, the COM+ Tracker Service Protocol server tracks out-of-process COM references (for more information, see [MSDN-COM]).

<3> Section 2.2.4: On Windows, reference-count statistics are collected for tracked conglomerations. Windows determines whether or not to track a conglomeration based on its per-conglomeration configuration, which can be modified by using the COM+ Remote Administration Protocol EventsEnabled property. For more information about this property, see the Conglomerations Table in [MS-COMA] section 3.1.1.3.6.

<4> Section 2.2.4: On Windows, reference-count statistics are collected for tracked conglomerations. Windows determines whether or not to track a conglomeration based on its per-conglomeration configuration, which can be modified by using the COM+ Remote Administration Protocol EventsEnabled property. For more information about this property, see the Conglomerations Table in [MS-COMA] section 3.1.1.3.6.

<5> Section 2.2.4: On Windows, pooling statistics are collected for tracked conglomerations. Windows determines whether or not to track a conglomeration based on its per-conglomeration configuration, which can be modified by using the COM+ Remote Administration Protocol EventsEnabled property. For more information about this property, see the Conglomerations Table in [MS-COMA] section 3.1.1.3.6.

<6> Section 2.2.4: On Windows, method call statistics are collected for tracked conglomerations. Windows determines whether or not to track a conglomeration based on its per-conglomeration configuration, which can be modified by using the COM+ Remote Administration Protocol EventsEnabled property. For more information about this property, see the Conglomerations Table in [MS-COMA] section 3.1.1.3.6.

<7> Section 2.2.4: Windows collects method call statistics in 1-second intervals and calculates the statistics over the four most recent intervals. The average response time for a component is calculated as the slowest average response time over all component instances in the instance container.

<8> Section 2.2.4: On Windows, method call statistics are collected for tracked conglomerations. Windows determines whether or not to track a conglomeration based on its per-conglomeration configuration, which can be modified by using the COM+ Remote Administration Protocol EventsEnabled property. For more information about this property, see the Conglomerations Table in [MS-COMA] section 3.1.1.3.6.

<9> Section 2.2.4: Windows collects method call statistics in 1-second intervals and calculates the statistics over the four most recent intervals.

<10> Section 2.2.4: Windows considers a method call successful if it returns a success result, as specified in [MS-ERREF] section 2.1.

<11> Section 2.2.4: On Windows, method call statistics are collected for tracked conglomerations. Windows determines whether or not to track a conglomeration based on its per-conglomeration configuration, which can be modified by using the COM+ Remote Administration Protocol EventsEnabled property. For more information about this property, see the Conglomerations Table in [MS-COMA] section 3.1.1.3.6.

<12> Section 2.2.4: Windows collects method call statistics in 1-second intervals and calculates the statistics over the four most recent intervals.

<13> Section 2.2.4: Windows considers a method call failed if it returns a failure result, as specified in [MS-ERREF] section 2.1.

<14> Section 2.2.4: On Windows, method call statistics are collected for tracked conglomerations. Windows determines whether or not to track a conglomeration based on its per-conglomeration configuration, which can be modified by using the EventsEnabled property described in [MS-COMA]. For more information about this property, see the Conglomerations Table in [MS-COMA] section 3.1.1.3.6.

<15> Section 3: For Windows XP and later and Windows Server 2003 and later, the COMT server exposes tracker events as a COM+ Event System Protocol event class (for more information, see [MS-COMEV] section 3.1.1.1) with the EventClassID {ECABB0C3-7F19-11D2-978E-0000F8757E2A}.

To receive tracker events from applicable Windows Server releases, a client application creates a COM+ Event System Protocol subscription object (for more information, see [MS-COMEV] section 3.1.1.2) with the following properties:

Property

Value

EventClassID

{ECABB0C3-7F19-11D2-978E-0000F8757E2A}

InterfaceID

{4E6CDCC9-FB25-4FD5-9CC5-C9F4B6559CEC}

The client application can set other subscription properties to values that are appropriate to the application. The client application then stores the subscription by calling the IEventSystem::Store method (for more information, see [MS-COMEV] section 3.1.4.1.2).

Note that the COMEV server on Windows might be unable to create a subscription if the subscriber interface is located on an object server that does not accept anonymous incoming calls. See [MS-COMEV] Appendix B Windows Behavior (section 7) for more information.

On Windows 2000 operating system, the COMT server does not support tracker events.

For Windows XP and later and Windows Server 2003 and later, the Component Services administrative tool creates such a subscription, setting the SubscriberInterface property to its implementation of IComTrackingInfoEvents by calling IEventSubscription::put_SubscriberInterface (for more information, see [MS-COMEV] section 3.1.4.4.14).

On Windows 2000, the Component Services administrative tool does not create a subscription to tracker events.

<16> Section 3: WindowsCOMT servers make calls to the IComTrackingInfoEvents interface as the machine account of the server.

<17> Section 3: For Windows XP and later and Windows Server 2003 and later, the COMT server stops sending tracker events to a client application when that application removes the subscription object it created.

A client application can do this by calling either the IEventSystem::Remove method or the IEventSystem::RemoveS method (for more information, see [MS-COMEV] sections 3.1.4.1.3 and 3.1.4.1.6, respectively).

On Windows 2000, the COMT server does not support tracker events.

For Windows XP and later and Windows Server 2003 and later, the Component Services administrative tool removes the subscription it created by calling IEventSystem::Remove:

On Windows 2000, the Component Services administrative tool does not create a subscription to tracker events.

<18> Section 3.1.1: On Windows, the Partition ID property is the ID property of the Partition (for more information, see [MSDN-Partitions]) for the COM+ application (for more information, see [MSDN-Applications]).

<19> Section 3.1.4.1: Opnums reserved for local use apply to Windows as follows:

opnum

Description

3

Returns E_NOTIMPL only. It is never used.

7

Returns E_NOTIMPL only. It is never used.

<20> Section 3.1.4.2.2: Windows COMT servers accept a value for the bstrDirectory parameter that is a path to a directory in the server’s local file system (for more information, see [MSDN-FILE]) or in Universal Naming Convention (UNC) representing a local or remote path. In addition, Windows COMT servers require paths to have a maximum length of 260 (MAX_PATH) Unicode characters.

<21> Section 3.1.4.2.2: Windows COMT servers enable the default dump file location to be configured for a conglomeration via the COMA protocol [MS-COMA]. This location is the conglomeration's DumpPath property as specified in [MS-COMA] section 3.1.1.3.6.

<22> Section 3.1.4.2.2: Windows COMT servers enable the default dump file limit to be configured for a conglomeration via the COMA protocol [MS-COMA]. This location is the conglomeration's MaxDumpCount property as specified in 3.1.1.3.6.

<23> Section 3.1.4.2.2: Windows COMT servers do not impersonate the client when attempting to determine the number of previously written dump files or when deleting a previously written dump file. Windows COMT servers do impersonate the client when writing the dump file.

<24> Section 3.1.4.2.2: Windows COMT servers write user-mode mini-dumps (for more information, see [MSDN-MDWD]). The file name used for these mini-dumps is of the form "ConglomerationIdentifier-YYYY_MM_DD_HH_mm_ss", where ConglomerationIdentifier is the CurlyBraceGuidString representation of the conglomeration identifier of the conglomeration corresponding to the specified instance container, and the remaining fields represent the date and time when the process dump was requested.

<25> Section 3.2.5.1.1: On Windows, a process is a Windows process. The ExeName property is the executable image file name.

<26> Section 3.2.5.1.1: The IsService property is TRUE (0x00000001) or FALSE (0x000000000) to indicate whether the process is a Windows service.

<27> Section 3.2.5.1.1: On Windows, an instance container is an instance of a COM+ application (for more information, see [MSDN-Applications]). The ApplicationType property is one of the following values:

Value

Meaning

0

A COM+ library application.

1

A COM+ server application.

2

Services without components.

<28> Section 3.2.5.1.1: On Windows, the Name property is the COM+ application name (for more information, see [MSDN-Applications]).

<29> Section 3.2.5.1.1: Windows collects method call statistics in 1-second intervals and calculates the statistics over the four most recent intervals. The average response time for a component is calculated as the slowest average response time over all component instances in the instance container.

<30> Section 3.2.5.1.1: On Windows, the Name property is the ProgId of the component (for more information, see [MSDN-COM]).