Tidal Enterprise Orchestrator: Remote Console Crashes in 64-bit OS

Available Languages

Updated:May 13, 2011
Document ID:112999

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 resolve Cisco Tidal Enterprise Orchestrator (TEO) remote console crashes when running the remote console on a 64-bit operating system (OS).

Prerequisites

Components Used

  • TEO 2.1+

  • Windows 64-bit OS

  • .NET Framework

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.

Problem

When running the remote console on a 64-bit OS, the console does not start or show as visible and displays .NET Runtime 2.0 errors. Other symptoms of a crash might be evident as well.

Solution

This is caused by a "clean" or unpatched .NET Framework install.

In order to resolve this problem, install all the relevant .NET Framework patches, including these two in particular:

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products