Tidal Enterprise Orchestrator: Cannot Import Automation Packs

Available Languages

Updated:October 25, 2011
Document ID:113284

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

This document describes how to troubleshoot the instance where a user cannot import an automation pack.

Prerequisites

Components Used

The information in this document is based on Tidal Enterprise Orchestrator (TEO) 2.1 or later.

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.

Automation Pack Import

Normally, a user can import an automation pack by going to Administration > Automation Packs, and right-clicking and selecting Import.

Problem

A common issue with importing is for the Import option to be greyed out or disabled.

Solution

Complete these steps in order to resolve this problem:

  1. Close down the TEO Master UI, and stop TEO.

  2. Make sure the user is a local administrator and a TEO administrator.

  3. Add the permission they are missing to their profile.

  4. Restart TEO, and Reopen the Master UI.

  5. The user should now be able to import automation packs.

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products