1
236

Written by

Evgeny Shvarov
Senior Startups and Community Programs Manager at InterSystems Corporation
TEAM
Follow
Article Evgeny Shvarov · Jun 29, 2025 1m read

REST API Debug: Page Not Found situation

#InterSystems IRIS #Debugging #Development Environment #REST API

Hi developers. Just want to share with you a finding that might save you a few important minutes of your developer life with InterSystems IRIS.

But!

It should work; you deployed the REST API correctly, and everything is just in place.

What can go wrong?

The issue in my case was that I misspelled the name of the class, like in this picture:

It was a typo there. And there were no compilation errors, no console messages - no evidence of what is wrong. 

So, if you face a similar problem - Not Found message for a page that "just should work" - take a look at the Dispatch class? if the name is accurate?

And of course ask the community. Maybe it will save you a few important minutes of our precious developers' life.

Cheers!

Discussion (4)1
Log in or sign up to continue

Comments

Kurro Lopez · Feb 19

Additionally, if you have a 401 – Unauthorized status, verify that you have granted the appropriate permissions.

0
Evgeny Shvarov  Feb 19 to Kurro Lopez

Thanks, @Kurro Lopez!  Agree!

The only moment - I don't recommend using %All in production as it is a very broad permission. 

0
Tani Frankel · Feb 22

Regarding your comment @Evgeny Shvarov: "there were no compilation errors, no console messages - no evidence of what is wrong.", in these HTTP (CSP/Web) kind of situations/problems it is recommended to use "CSP Logging" (aka ISCLOG).

If you turn on the %ISCLOG you should be able to see the error you are getting.

For example if I changed my REST dispatch class from the correct: 'Demo.Debug.REST' to a non-existent: 'Demo.Debug.REST11', and try and call my service, I can see from the ISCLOG-based table -

%SYS>>SELECT ID, Category, LogLevel, Message FROM %Library.SysLogTable WHERE Message [ 'ERROR'

| ID | Category 	| LogLevel  | Message 					|
| -- | -- 		| -- 	    | -- 						|
| 39 | CSPServer 	| 2         | [HandleError]: ERROR #5002: ObjectScript error: <CLASS DOES NOT EXIST>CSPDispatch+147^%SYS.cspServer *Demo.Debug.REST11 |

So you can see you would be able to observe you are getting a <CLASS DOES NOT EXIST> error, and the name of the class it is trying to access.

(Of course there are other entries in the log, before, and after this entry, that can also help you relate this error to the URL you are trying to access)

0