WIP COM Warning Events

Microsoft.HostIntegrationServer.2013.WIP_COM_WarningEvents (Rule)

Captures warning events and generates a warning alert

Knowledge Base article:

Summary

Event 102 - Transaction Integrator has encountered a problem executing the method call. The details of the problem have been returned to the calling application in an exception. The details of the exception are described in the event text.

Event 103 - This event will be logged if an error occurs during creation of the TI object. When this event occurs, the TI runtime returns CLASS_E_CLASSNOTAVAILABLE to the client and includes the details of the error in this event.

Event 104 - An error occurred when trying to invoke a method on a TI WIP object. The underlying HRESULT that occurred during the Invoke process is contained in the event text.

Event 112 - Transaction Integrator detected an internal inconsistency and has terminated the process to avoid the risk of further corruption in this process. The problem may be caused by a bug in Transaction Integrator or by bugs in any other components running in the same package. This event will be followed in the log by an event from COM+, because of the exception generated by Transaction Integrator to force process termination.

Event 113 - Transaction Integrator was unable to map the component CLSID specified in the event to a component library, or was unable to locate or load the component library that was found.

Event 114 - Transaction Integrator cannot create an instance of the object whose ProgId & CLSID are included in the event because the component is not currently assigned to a Remote Environment.

Event 115 - A TI WIP Object using 2PC (two phase commit) processing encountered an error during transaction commit processing which couldn't be reported to the client application.

Event 116 - Transaction Integrator was unable to initialize its management objects.

Causes

Event 102 - There are various causes for this event. The specifics are contained in the exception details outlined in the event.

Event 103 - This error may be caused by an installation or configuration error.

Event 104 - The HRESULT indicates the underlying cause of the problem.

Event 113 - A Transaction Integrator component library previously registered with MTS has been deleted or renamed

Other system configuration problems in the registry

Event 114 - Transaction Integrator cannot create an instance of the object whose ProgId & CLSID are included in the event because the component is not currently assigned to a Remote Environment.

Event 115 - An automation exception was formatted but couldn't be returned to the client because the error occurred after the method completed. The exception included in the event describes the error. Look for other events that indicate the outcome of the transaction.

Event 116 - The Transaction Integrator runtime DLL was unable either to create its management object or to initialize it. The HRESULT shown in the event indicates the cause of this error.

Resolutions

Event 102 - Use the exception details to identify and resolve the root cause of the problem.

Event 103 - Verify that the TI runtime is installed on the machine and that the TI object has been properly installed using the TI Manager. Examine the exception details for further information about the root cause of the problem.

Event 104 - Examine the returned HRESULT to obtain further information about the underlying problem. Based on the HRESULT, take appropriate steps to resolve the problem. Enabling TI tracing may also provide more detail about which step in the Invoke process failed.

Event 112 - Reconfigure your COM+ applications to isolate suspected components in their own application.

If all Transaction Integrator components are running alone in an application and the problem persists, contact Microsoft customer support.

Event 113 - Verify the component library for your component CLSID has not been deleted, moved, or renamed since it was registered with MTS.

Event 114 - Using TI Manager, assign the component to a Remote Environment

It is also possible to use the ClientContext object to specify a Remote Environment at runtime

Event 115 - The error may be caused by communication problems or configuration errors on your system. See the exception description for more information or corrective actions.

Event 116 - The error may be caused by corrupted system files or registry entries. Run the Configuration Wizard to attempt to reconfigure Transaction Integrator. If the problem persists, remove and reinstall the Transaction Integrator feature of Host Integration Server. If the problem still persists, contact Microsoft customer support.

Element properties:

Target

Microsoft.HostIntegrationServer.2013.WIP

Category

EventCollection

Enabled

False

Event Source

COMTI

Alert Generate

True

Alert Severity

Warning

Alert Priority

Normal

Remotable

True

Alert Message

WIP Alert for COM Warning Events

Server: {0}
Event ID: {1}
Event Description: {2}

Event Log

Application

Member Modules:

ID	Module Type	TypeId	RunAs
DS	DataSource	Microsoft.Windows.EventProvider	Default
Alert	WriteAction	System.Health.GenerateAlert	Default
WriteToDB	WriteAction	Microsoft.SystemCenter.CollectEvent	Default
WriteToDW	WriteAction	Microsoft.SystemCenter.DataWarehouse.PublishEventData	Default

Source Code:

<Rule ID="Microsoft.HostIntegrationServer.2013.WIP_COM_WarningEvents" Enabled="false" Target="Microsoft.HostIntegrationServer.2013.WIP" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>Application</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="String">Channel</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="String">Application</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>MatchesRegularExpression</Operator>

              <Pattern>^(102|103|104|112|113|114|115|116)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="String">PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="String">COMTI</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectEvent"/>

    <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>

    <WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertMessageId>$MPElement[Name="AlertMessageID8a9596a714a2441e85c2750bcc883699"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/LoggingComputer$</AlertParameter1>

        <AlertParameter2>$Data/EventDisplayNumber$</AlertParameter2>

        <AlertParameter3>$Data/EventDescription$</AlertParameter3>

      </AlertParameters>

    </WriteAction>

  </WriteActions>

</Rule>