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.
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).
Windows 64-bit OS
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.
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.
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:
Microsoft .NET Framework 3.5 Family Update for Windows XP x64, and Windows Server 2003 x64
Microsoft .NET Framework 3.5 Family Update for Windows Vista x64, and Windows Server 2008 x64