Error: 'Execute could not be completed' in WCC ECLI screen․

Products

• Autosys Workload Automation

Issue/Introduction

You encounter "Error: 'Execute could not be completed'" when using the Enterprise Command Line (ECLI) screen in Web Control Center (WCC) on a secondary HA host.
This issue typically surfaces after restarting services or changing application passwords.​​​​​​​‌​​​​

ERROR MESSAGE:

"Error: 'Execute could not be completed.'"

SYMPTOMS:

• ECLI screen fails on the secondary WCC host while the primary host works correctly.

• Java NullPointerException appears in the commandapp.log.

CONTEXT: This occurs during post-restart validation of WCC screens in a High Availability (HA) environment.

IMPACT: Users cannot execute commands through the WCC ECLI interface on the affected secondary node.

Environment

 

• AutoSys: 12․1 SP1

• EEM Version: 12․6․6

• WCC Version: ae-webui-12․1․01

• Platform: Unix 

 

Cause

ROOT CAUSE: The issue is likely caused by a synchronization or authentication failure within the EEM multi-write configuration or a stale security artifact in the WCC application cache.

Resolution

PREREQUISITES:

• Access to EEM and WCC server service management.

• Administrator credentials for the application environment.

STEPS:

1. RESTART AUTHENTICATION AND WEB SERVICES:

   Action: Stop and restart the Embedded Entitlements Manager (EEM) on the secondary host, followed by a restart of the WCC instance.

   EXPECTED: The ECLI screen should function without the 'Execute' error.
   NOTE: This action may need to be performed outside of business hours if it impacts production availability.

2. COLLECT DIAGNOSTICS IF RESTART FAILS:

   If the service restart does not resolve the issue, collect the following for support:

   • Output of "netstat -ano | grep 5250" from both EEM servers.

   • IP addresses for all EEM and WCC servers.

   • AEWS logs from the Autosys Event Server.

   • Zipped CA Directory logs, EEM logs, and iTechnology logs from both hosts.

VERIFY SUCCESS:

• Log into the secondary WCC host.

• Navigate to the ECLI screen.

• Execute a test command.

• Confirm the command completes without the "Execute could not be completed" error.