Tidal Enterprise Orchestrator: OLEDB Drivers Not Detected After Installation of TEO 2.2

Available Languages

Updated:October 4, 2011
Document ID:113268

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 discusses OLEDB driver compatibility with Tidal Enterprise Orchestrator (TEO) 2.1 and 2.2.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is written for Tidal Enterprise Scheduler 2.1 and 2.2.

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.

Symptoms

TEO does not recognize the installed OLEDB drivers.

Status

This may be especially noticeable after an OLEDB connection in 2.1 that works, but fails in version 2.2.

Resolution

Although no specific drivers are recommended, it is important to make sure the correct version of the drivers are installed.

Tidal Enterprise Orchestrator 2.1 requires 32bit OLEDB drivers.

Tidal Enterprise Orchestrator 2.2 requires 64bit OLEDB drivers.

If you upgrade from 2.1 to 2.2 you need to make sure that 64bit OLEDB drivers are installed.

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products