API-1019: Could not process the request due to internal error

book

Article ID: 186192

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM On Premise Clarity PPM SaaS Clarity PPM SaaS

Issue/Introduction

When navigating to the details page on some projects, the following error is thrown in the UI: 

API-1019: Could not process the request due to internal error.

The error in the app-ca log includes the following: 

ERROR 2020-03-10 12:00:00,632 [https-jsse-nio2-443-exec-8] lookup.LookupTypeCache (clarity:admin:12345678__E1C2300A-4B00-4DE4-A2BC-D0D000A20000:PPM_REST_API) Invalid lookup type: <lookup code>

ERROR 2020-03-10 12:00:00,632 [https-jsse-nio2-443-exec-7] ppm.rest (clarity:admin:12345678__E1C2300A-4B00-4DE4-A2BC-D0D000A20000:PPM_REST_API) Exception processing request for resource [projects], query string [/projects/6000001]
java.lang.NullPointerException...

Cause

This error will occur if there is an API enabled attribute in the system that references a lookup that does not exist. The lookup being the one referenced in the first part of the errors in the logs.

Environment

Release : 15.7

Component : CA PPM APPLICATION

Resolution

In order to no longer get the error on the Details page of the projects, clear the API Attribute ID on the project attribute referencing this lookup. 

Additional Information

This can happen on any OOTB object/custom object that is API enabled.

Another example of log file:

ERROR 2021-08-27 17:21:57,506 [http-nio-8080-exec-32] lookup.LookupTypeCache (clarity:myuser:5594733__1349586A-823A-4124-A609-07FA8B9281C1:PPM_REST_API) Invalid lookup type: YES_NO
ERROR 2021-08-27 17:21:57,507 [http-nio-8080-exec-32] lookup.LookupControllerImpl (clarity:myuser:5594733__1349586A-823A-4124-A609-07FA8B9281C1:PPM_REST_API) Lookup: YES_NO doesn't exist
ERROR 2021-08-27 17:21:57,508 [http-nio-8080-exec-32] ppm.rest (clarity:myuser:5594733__1349586A-823A-4124-A609-07FA8B9281C1:PPM_REST_API) Exception processing request for resource [describe], query string [/describe/custObject?_cb=1630077717316]
java.lang.NullPointerException