Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect to IRIS for Health 2023.1.2 server #1462

Open
Santiagf opened this issue Nov 27, 2024 · 7 comments
Open

Unable to connect to IRIS for Health 2023.1.2 server #1462

Santiagf opened this issue Nov 27, 2024 · 7 comments

Comments

@Santiagf
Copy link

Type: Bug

Click on Intersystems icon on left side of VSCode panel
Click + to add a server
Enter Server information: Server name, Scheme, Host, port
Attempt to connect.
Response: Unavailable

Extension version: 2.12.10
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info
Item Value
CPUs 12th Gen Intel(R) Core(TM) i5-1245U (12 x 2496)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 15.64GB (1.83GB free)
Process Argv --crash-reporter-id 666bbe59-e0be-44dc-993b-3bc3b7acab2f
Screen Reader no
VM 0%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

@isc-bsaviano
Copy link
Contributor

@Santiagf Are you sure you entered your connection information correctly? If you open the developer tools using the Developer: Toggle Developer Tools command from the command palette, do you see any errors in the Console that appears?

@Santiagf
Copy link
Author

Santiagf commented Nov 27, 2024 via email

@isc-bsaviano
Copy link
Contributor

@Santiagf 401 means "Unauthorized". That usually means you didn't supply a username or password, or one or both were incorrect. Since you say those credentials work for the SMP that seems unlikely though. You can test the REST request that VS Code is making to IRIS from your browser to see what the error is. In your browser, open the SMP page , replace csp/sys/UtilHome.csp with api/atelier/, and press enter. Enter your username and password when prompted by the browser. If everything is working OK, you should see some JSON that includes system information like your IRIS $ZV. If you don't see that info, you should see an error of some sort.

@Santiagf
Copy link
Author

Santiagf commented Nov 27, 2024 via email

@isc-bsaviano
Copy link
Contributor

@Santiagf That response is definitely unexpected. Since you're seeing the same behavior from the browser as VS Code, I don't think this is a VS Code issue. Can you open your user definition on the IRIS portal and see if you have the %Developer role or %Development resource? The Atelier API requires USE permission on %Development.

@Santiagf
Copy link
Author

Santiagf commented Nov 28, 2024 via email

@gjsjohnmurray
Copy link
Contributor

gjsjohnmurray commented Nov 28, 2024

@Santiagf I suggest you use IRIS Portal's System Administration > Security > Auditing section to look for information in the audit log. Make sure that the %System/%Login/LoginFailure audit event is enabled when you reproduce the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants