I expect the IRIS Portal URLs for these two instances look like this:

In that case, use the bold section as the "pathPrefix" property within the "webServer" object in the server's entry in the "intersystems.servers" settings object.

When setting up a connection definition step-by-step this part is referred to as Path prefix of instance.

See https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cls...

This is caused by how version 2.12.0 and above of the ObjectScript extension depends on the Server Manager extension, which hasn't yet been made compatible with VS Code in the browser.

I have created https://github.com/intersystems-community/intersystems-servermanager/iss...

Workaround is to use the gearwheel on the extension's detail page, then choose to install the latest pre-2.12 version.

Maybe the page is trying to display details of a previously-opened prodclass that is giving it a problem.

I suggest you use the %G utility in an IRIS Terminal in your namespace (INTERFACES?) to see what this lists:

INTERFACES>d ^%G
 
Device:
Right margin: 80 =>
Screen size for paging (0=nopaging)? 24 =>
For help on global specifications DO HELP^%G
Global ^EnsPortal.Settings(,"LastProduction")
^EnsPortal.Settings("XXX","LastProduction")="Foo.Bar"
 
Global ^

I came up with a better technique for using Yuzinji and Structure101g Studio to reveal which deprecated classes an app's codebase uses. Here's a screenshot showing the results for the Web Terminal 4.9.6 package on IRIS 2024.1

I adapted the tagging technique to identify the use of deprecated methods in non-deprecated classes. In the case of the Web Terminal codebase, no such usage was found.

If anyone reading this is interested in trying this on your own codebase please contact me through DC's DM facility, or email info@georgejames.com