Tidal Enterprise Scheduler: Error 1720 Received when Tidal Agents Upgraded on the Server

Available Languages

Download Options

  • PDF     (5.6 KB)
    View with Adobe Reader on a variety of devices
Updated:October 10, 2012
Document ID:113641

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 provides instructions on how to resolve Error 1720 when you upgrade the Tidal Agent.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • An existing Tidal Agent 3.0 or higher installation

  • Administrator privileges on the system

Components Used

The information in this document is based on Tidal Windows Agent version 3.0 or higher.

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.

Problem

When you upgrade an existing Tidal Windows Agent 3.0 or higher installation, the installation fails with error code 1720.

Solution

Complete these steps:

  1. Make sure the existing Agent is stopped before trying to install the new one.

  2. Uninstall the old Agent before installing the new one.

  3. Install the Agent as an Administrator.

  4. Install the Agent manually using this code:

    Msiexec /I <Path_to_MSI> NOVBSCRIPT="True" /L C:\temp\agentinstall.log

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco