ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

The command "conda init" is failing when executed using Automic Windows Command Action Pack

book

Article ID: 186722

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The command "conda init" is failing when executed using Automic Windows Command Action Pack. The error message in the report log is the following:

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If using 'conda activate' from a batch script, change your
invocation to 'CALL conda.bat activate'.

To initialize your shell, run

    $ conda init <SHELL_NAME>

Currently supported shells are:
  - bash
  - cmd.exe
  - fish
  - tcsh
  - xonsh
  - zsh
  - powershell

See 'conda init --help' for more information and options.

IMPORTANT: You may need to close and restart your shell after running 'conda init'.

Cause

The conda command has bug which prevents the command "conda init" from working properly.

Environment

Release : 12.x

Component : AUTOMATION ENGINE, CDA, Automic Windows Commands Action Pack

Resolution

-As a first troubleshooting step, please execute the command "conda init" outside One Automation and see if that works.

-Please check if your conda version is the latest one