search cancel

API-1003 error on describeAttributes


Article ID: 186996


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


Some users might get an API-1003 error sporadically and intermittently (see attachement).
What might cause the API error on the describeAttributes?



Clarity PPM 15.7


The describeAttributes is a metadata api which is public and viewable by all logged in users.
The fact that the grid does not render, could mean that this api call has failed and the page is unable to render the grid. It could also mean that a JavaScript syntax error was encountered and the constructed api url is incorrectly assembled and caused the api failure.

The metadata is fetched from the saved view, construct the grid (columns, sorting, grouping, filter settings, pinning, columns widths, etc), then make the data call and populate the rows.
As the failure happened in metadata, which is very uncommon, most probably a JavaScript runtime error occurred,

We would need the devtools console and network tab contents to confirm.

Additional Information

On a given case scenario, those API-1003 error on describeAttributes was caused by an app service not being properly up and running.

The app-system.log file of the given app server was showing following errors:

2020/06/25 13:46:26.079 | Caused by: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01403: no data found
2020/06/25 13:46:26.079 | ORA-06512: at "CLARITY_USER.CMN_SESSIONS_INS_ID_SP2", line 14
2020/06/25 13:46:26.079 | ORA-06512: at line 1
2020/06/25 13:46:26.079 | 

And the Developer tools showed HTML error 404 and when viewing the response header, the message is:
{"resourceId":null,"httpStatus":"404","errorMessage":"API-1003 : Could not find resource resourceProfiles.","errorCode":"api.invalidResource"}

Restarting the app service of the affected server resolved the issue

Other similar API-1003 error

API-1003 (attachments) when uploading documents to the Modern UX


1584714915881__errorAPI1003.png get_app