Tidal Enterprise Orchestrator: Windows Script Execution Does Not Work Properly in x64 Environments

Available Languages

Updated:March 1, 2011
Document ID:112178

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

Running Windows scripts in x64 environments continuously can cause them to become very delayed or stop working in general.

Prerequisites

Components Used

The information in this document is based on these software and hardware versions:

  • Tidal Enterprise Orchestrator 2.1 or later

  • Windows x64

Conventions

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

Problem

Running Windows scripts in x64 environments can result in the scripts taking extremely long or not working at all. The problem is due to a memory leak in LSASS.exe and is confirmed by this Microsoft article icon_popup_short.gif.

Solution

Go to this Microsoft article icon_popup_short.gif, and download and install the hotfix. This will help alleviate some of the memory leakage coming from LSASS.exe.

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products