Tidal Enterprise Orchestrator: Windows Event Trigger Does Not Register

Available Languages

Download Options

  • PDF     (5.7 KB)
    View with Adobe Reader on a variety of devices
Updated:March 1, 2011
Document ID:112179

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

When attempting to monitor a Windows event on another Windows server, the event trigger does not register.

Prerequisites

Components Used

  • Tidal Enterprise Orchestrator (TEO) 2.1 or later

  • Windows Trigger

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

The Windows event trigger does not register with the TEO Server. This error message may be seen:

The RPC server is unavailable.
	 (Exception from HRESULT: 0x800706BA)

Solution

Three WMI firewall rules must be enabled to allow passage through the firewall. This configuration should be performed on the TEO server.

Windows 2008

Perform these steps for Windows 2008:

  1. Click Start > Server Manager.

  2. Go to Configuration > Windows Firewall > Inbound Rules.

  3. In order to allow inbound of these components, right-click on them and allow enable of rule:

    • WMI (Async-In)

    • WMI (DCOM-In)

    • WMI (WMI-In)

Windows 2003

Perform these steps for Windows 2003:

  1. Click Start > Control Panel > Windows Firewall.

  2. Click the Exceptions tab, choose the WMI check box, and click OK.

Related Information

Revision History

Revision Publish Date Comments
1.0
01-Mar-2011
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products