Unable to deploy JIL through ECLI in Autosys WCC

Products

• Autosys Workload Automation

Issue/Introduction

Users are unable to deploy JIL (Job Information Language) using the Enterprise Command Line Interface (ECLI) within Autosys WCC on a Windows OS. This failure prevents users from creating jobs and can lead to delays in production deployment.

When attempting to deploy, the following error message is displayed:

Logon failure: the user has not been granted the requested logon type at this computer. StatusCode: 500, URL: https://examplehostname:9443/AEWS

 

Environment

Product: Autosys Workload Automation

Operating System: Windows

Component: ATSYS

Cause

This issue occurs due to an environment configuration problem where the specific Windows OS account is missing the necessary "Allow log on through Remote Desktop Services" permission on the AutoSys Windows server

Resolution

To resolve this issue and restore ECLI functionality, you must grant the missing Remote Desktop Services logon permission:

1. Identify the exact OS/Windows account used when the user runs ECLI.

2. Have your Windows administrator grant that account both the "Allow log on locally" and "Allow log on through Remote Desktop Services" user rights via Local Security Policy or Group Policy on the AutoSys Windows server.

3. Reboot the server after the rights are applied to ensure the changes take effect.

4. Retry the JIL deployment through ECLI.

Additional Information

Allow log on locally - security policy setting

Allow log on through Remote Desktop Services