ECLI Command Execution Isssue - Failed to log on using the given credentials. StatusCode: 500

Products

• Autosys Workload Automation

Issue/Introduction

While executing command on ECLI getting the below error

Failed to log on using the given credentials.
StatusCode: 500, URL: https://host1234:9443/AEWS,https://host5678:9443/AEWS

 

INFO   | jvm 1    | 2022/01/24 06:53:40 |   190185 | @configui <pool-22-thread-1> [] ERROR #VerificationManager                
# Exception caught trying to login to AutoSys server (ServerAutosys-Name): E180011 Login failed using: User=AUTOSYS-USER Password=<hidden>

INFO   | jvm 1    | 2022/01/24 06:58:47 |   190491 | StatusCode: 500, URL: https://host1234:9443/AEWS,https://host5678:9443/AEWS
INFO   | jvm 1    | 2022/01/24 06:58:47 |   190491 | com.ca.wcc.command.client.webserver.WebServerException: Failed to log on using the given credentials.
INFO   | jvm 1    | 2022/01/24 06:58:47 |   190491 | StatusCode: 500

INFO   | jvm 1    | 2022/01/24 07:04:50 |   191756 | INFO: CsrfGuard analyzing request /wcc/configuration/JavaScriptServlet
INFO   | jvm 1    | 2022/01/24 07:04:52 |   191758 | @configui <pool-29-thread-1> [] ERROR #VerificationManager                # Exception caught trying to login to AutoSys server (ServerAutosys-Name): E180011 Login failed using: User=AUTOSYS-USER Password=<hidden>

 

Environment

Release : 12.0

Component : CA Workload Automation AE (AutoSys)

Resolution

• The credential user's password must be consistent across both of the as_server and aews servers and properly defined in WCC.
• When specifying a global credential to be used by the ECLI, that ID must be a valid account on the AutoSys server.
• The monitor ID only has to exist within EEM and does not have to be a valid local account on the AutoSys server. This is why you could run into a scenario where the monitor ID works fine but doesn't work if it is used as a global credential.
• Additionally, check for passwords.  Passwords  ending with "\" may also cause issues.

 

Additional Information

If the error still continues:

1) delete the Credential user,

2) logout of WCC and Login to WCC

3) create the credential user, validate

4) logout of WCC and Login to WCC

5) retest ECLI again