Tidal Enterprise Scheduler: Jobs Cannot Be Scheduled or Inserted in to Schedule After Being Transported via Transporter

Available Languages

Download Options

PDF (5.6 KB)
View with Adobe Reader on a variety of devices

Updated:January 23, 2012

Document ID:113399

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

Prerequisites

Requirements

Components Used

Conventions

Why jobs cannot be scheduled after being transported using Transporter

Related Information

Introduction

This document provides information about a common scenario where jobs or job groups cannot be scheduled after being transported using Transporter.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This information assumes a 5.3.1 master.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Why jobs cannot be scheduled after being transported using Transporter

Transporter for 5.3.1 is a product that is installed via a setup program. The purpose is to move jobs, action, events, etc from one database to another. The complete program consists of executables and dlls. Xporter.exe is responsible for moving the jobs and other objects. Tsencrypt.dll is responsible for notifying the master of the new arrival of jobs and other objects.

It is possible to run Transporter simply using the executable, Xporter.exe. However, if the complete installation of the product does not take place, the tsencrypt.dll is not installed. Without this component, the master will not find the newly transported jobs at schedule time and will not schedule them.

Therefore, the most common reason why jobs cannot be scheduled after they have been transported is due to using the Xporter.exe executable by itself and not the completely installed product.