Tidal Enterprise Orchestrator: Powershell CLI Breaks When Machine Name is Changed

Available Languages

Updated:May 6, 2011
Document ID:112948

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

You receive a "Process?WSDL cannot be found" error and are unable to use the Powershell CLI when you change the name of your machine or domain while you are using the Powershell CLI.

Prerequisites

Components Used

The information in this document is based on the TEO 2.1+ , Windows Powershell 1.0+.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

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

Solution

The Powershell CLI must point to the correct HTTP endpoint for the WSDL and the TEO service.

Complete these steps in order to resolve this issue:

  1. Go to the TEO install directory (for example, C:\Program Files (x86)\Cisco\Tidal Enterprise Orchestrator).

  2. Open the Tidal.Automation.CLI.CorePSSnapin.dll.config file.

  3. Find the WebService Uri tag, and change the HTTP endpoint to your new or current HTTP endpoint

  4. If necessary, register again your CLI plug-in by running the Tidal.Automation.CLI.CorePSSnapin.Register.vbs script located in the TEO install directory.

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products