search cancel

User getting unable to import JIL through WCC

book

Article ID: 229798

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

A user attempting to import a jil script via the WCC, is getting the following error. 

Unexpected problem connecting to Server
StatusCode: 400, URL: https://aews-IT2.test.tiaa-cref.org/AEWS

I confirmed I was able to import a jil script. I also confirmed via EEM permission check that the user should be able to import jobs to the environment. The environment is Open to all users to create jobs.  I had the user switch to chrome browser, he was using Edge. I recycle the WCC services, app service and web service. Without any luck. 

He imported jobs 4 days earlier. I was also able to import jobs using a test ID that belongs to the same AD group. 

Environment

Release : 12.0

Component : WORKLOAD CONTROL CENTER

Resolution

You only fill in the "Name" field on the ECLI if you are trying to export a job.
In that case you provide the name of the job to be exported.

If you are attempting to import a job you only fill in the "File name" which is the path and filename of the file that contains the jil.

In BOTH situations you fill in the "Server".

In the screen prints if there were any errors they would be further down in the Errors section.   

Support tried using the jil file provided and saw the error the end user saw.
The reason for the error was the file contained control characters between the two jobs.
There were/are two null characters, once removed the error went away and the jobs were imported in without futher issue.