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.
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.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
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:
Go to the TEO install directory (for example, C:\Program Files (x86)\Cisco\Tidal Enterprise Orchestrator).
Open the Tidal.Automation.CLI.CorePSSnapin.dll.config file.
Find the WebService Uri tag, and change the HTTP endpoint to your new or current HTTP endpoint
If necessary, register again your CLI plug-in by running the Tidal.Automation.CLI.CorePSSnapin.Register.vbs script located in the TEO install directory.