Tidal Enterprise Scheduler: Install .NET 2.0 Error Message

Available Languages

Updated:November 4, 2011
Document ID:113301

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 an issue in Cisco Tidal Enterprise Scheduler (TES) that occurs when you install the Windows Agent and receive an error that states you must install .NET 2.

Prerequisites

Requirements

You must be logged in as local administrator to complete the procedure in this document.

Components Used

The information in this document is based on the Cisco Tidal Enterprise Scheduler Agent 3.x.

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 information on document conventions.

Problem

If you install .NET 4.0 and reboot the server after the installation, you might receive an error that states .NET 2.0 must be installed.

This issue occurs because .NET 4.0 does not install all components from previous .NET versions. Since the installation of .NET 4.0 is not cumulative, you must install each version of .NET.

Solution

Cisco Tidal Enterprise Scheduler requires only .NET 2.0. If you have installed, earlier or later versions of .NET, you must install .NET 2.0 as well.

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco