vscode failed to fetch namespace list from server
1. vscode extensions : intersystems.language-server-2.8.0@linux-arm64.vsix
2. api/atelier web application is enabled

3. vscode connect failed.

Comments
To address the issue of failing to fetch the namespace list from the server in VS Code using the InterSystems Language Server extension, you can try the following steps:
Ensure you have correctly configured the server settings in your
settings.jsonfile, which should include the server name, namespace, and credentials. Below is a sample configuration for reference:{ "objectscript.conn": { "server": "your_server_name", "ns": "USER", "active": true }, "intersystems.servers": { "your_server_name": { "webServer": { "scheme": "http", // or "https" depending on your server "host": "your_host_address", "port": your_port_number }, "username": "your_username", "password": "your_password" } } }Replace
your_server_name,your_host_address,your_port_number,your_username, andyour_passwordwith your actual connection details. Ensure that the namespace you are trying to connect to is available on the server and accessible with your credentials [1][2].Verify that the namespace exists on the server. If the namespace you set in the configuration has been deleted or does not exist, VS Code may fail to fetch the list or connect. You can recreate the namespace temporarily on the server, which may help resolve the issue and allow you to switch namespaces via the UI [3].
Confirm that the web application
api/atelieris correctly enabled on the server. If it is not properly configured, the connection might fail.If the issue persists, try using the "Choose Server and Namespace" functionality in the ObjectScript Explorer view to manually select or update the namespace [4].
If none of these steps resolve the issue, seeking guidance in the InterSystems Developer Community might be necessary.
Sources:
1. namespace is available on the server
2.api/atelier is correctly enabled on the server
if your VS Code with the InterSystems Language Server isn’t fetching the namespace list, and you’ve confirmed the namespace exists and api/atelier is enabled, the next things to check are usually around connection config +network/auth:
make sure settings.json has the correct server, port, scheme (http vs https), and credentials. even small typos or wrong case in username/password can block fetching.
try using “Choose Server and Namespace” in ObjectScript Explorer — sometimes the cached connection info trips the extension up.
check for any firewall or proxy on Ubuntu ARM64 that could be blocking the VS Code extension from reaching the web app.
confirm the extension version (2.8.0) is fully compatible with IRIS 2024.3; occasionally newer IRIS builds need the latest language server release.
basically, the extension looks fine, so it’s almost always a config or network hiccup, not a namespace/server issue.
- The
curlcommand on the local machine can retrieve the correct response fromapi/atelier. - The latest plugin management package
intersystems-community.servermanager-3.10.5.vsixis being used. - VS Code OUTPUT: The ObjectScript panel outputs "ERROR: write EACCES". It is inferred that this may be a startup permission issue with the VS Code user; however, VS Code cannot start normally when run as the root user.
3. vscode connect failed.
It looks like your images failed to upload so it's not clear what (if any) errors you are getting when the connection failed.
OUTPUT:ObjectScript
ERROR: write EACCES
Are you using http or https?
using http
Try logging into the System Management portal with that user, assuming the user has access to do so. If you can log in. Try to switch namespaces and see if you can see the list of namespaces.
One other thing to check is that your user or a role your user is part of has SQL Procedure access to %Library.RoutineMgr_StudioOpenDialog in %SYS
.png)
4.Sure enough, even after enabling the proxy for Cursor, it still reports "failed to retrieve the namespace".Once these configurations are commented out, the connection works normally.
"http.proxy": "http://127.0.0.1:7890",
"cursor.general.disableHttp2": true