REST objects function throws Unsupported type:-1 for type JOBS
search cancel

REST objects function throws Unsupported type:-1 for type JOBS

book

Article ID: 206998

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Unable to import a JOBS object via REST API call. It's possible to import JOBP and JOBF no problem but this error is thrown for the type JOBS:

0210120/114120.545 - 43     U00045105 Log on of 'REST/API' successful.
20210120/114120.561 - 43     U00045197 FileSync: Import object 'JOBS.WIN01.TEST.X' of type 'JOBS'
20210120/114120.561 - 43     U00045014 Exception 'java.lang.IllegalArgumentException: "Unsupported type:-1"' at 'com.automic.database.impl.TypeConverter.convertFromString():160'.
20210120/114120.561 - 43     U00045099 The server replied with following status: '500'

A Rest=9 trace on the JCP shows:

20210120/161648.959 - 43     U00045105 Log on of 'REST/API' successful.
20210120/161649.116 - 43     U00045197 FileSync: Import object 'JOBS.WIN01.TEST.REST' of type 'JOBS'
20210120/161649.162 - 43     U00045014 Exception 'java.lang.IllegalArgumentException: "Unsupported type:-1"' at 'com.automic.database.impl.TypeConverter.convertFromString():160'.
20210120/161649.162 - 43     U00045099 The server replied with following status: '500'
20210120/161649.162 - 43               Response-Headers: [Content-Type=application/json]
20210120/161649.162 - 43               Response-Payload:
20210120/161649.162 - 43               {
20210120/161649.162 - 43                 "code" : 45110,
20210120/161649.162 - 43                 "error" : "An Automation Engine internal error occured.",
20210120/161649.162 - 43                 "details" : "No detail information available."
20210120/161649.162 - 43               }

Environment

Release : 12.3

Component : AUTOMATION ENGINE

DB: SQL Server

Resolution

This is caused by an old JDBC driver in the automation engine's \lib directory (pointing to SQL Server) - the JDBC driver being used was 2.0 instead of 6.0. Once it was updated, the REST call worked correctly.