Unable to see saved connections in Restricted Mode

[krishanth3]

Issue Type: Bug

I am unable see saved sql server connections nor able to establish a new connection. Even recent connections are not available. All places just show "Loading..." text.

Azure Data Studio version: azuredatastudio 1.33.0 (6783aa6, 2021-10-26T17:28:15.782Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: Yes

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz (8 x 2304)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.61GB (15.61GB free)
Process Argv
Screen Reader	no
VM	0%

Extensions: none

[krishanth3]

[choelterati]

Can confirm I'm also experiencing this issue on Windows 10 since yesterday.

[github-actions]

We need more info to debug your particular issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

There are two types of logs to collect:

Console Logs

• Open Developer Tools (Help -> Toggle Developer Tools)
• Click the Console tab
• Click in the log area and select all text (CTRL+A)
• Save this text into a file named console.log and attach it to this issue.

Application Logs

• Open command palette (Click View -> Command Palette)
• Run the command: Developer: Open Logs Folder
• This will open the log folder locally. Please zip up this folder and attach it to the issue.

[kburtram]

@choelterati @krishanth3 are you seeing any errors in the "Help->Toggle Developer Tools" Console? Are these all connections to SQL Server/Azure SQL DB? Also, could you please restart with extensions disabled and see if that helps?

[choelterati]

I'm not running any extensions, but I am seeing errors in the dev tools console log. Attached is an image and a txt log of them all.

azure data studio console errors.txt

[kburtram]

@choelterati thanks for the additional context. This appears to be the same issue as #17530. You can try the workaround I suggested on that issue which may clear out some invalid state triggering this bug. Note the path in the other issue is for mac, for windows the corresponding location would be C:\Users[USERNAME]\AppData\Roaming\azuredatastudio.

We're continuing to investigate and get an internal repro. The callstack seems to be complaining about https://github.com/microsoft/azuredatastudio/blob/main/src/sql/workbench/services/connection/browser/connectionDialogService.ts#L308 but not clear why capabilities would be null there.

Please let us know if you can think of any other customization or configuration that may be helpful in determining what's going on.

[Charles-Gagnon]

@kburtram I wonder if this is something to do with the Workspace Trust? The behavior shown in the screenshot (everything showing as loading) is what happens when you don't "trust" a workspace (since it doesn't load any extensions when that happens...)

For people in the thread - do you see the "Restricted Mode is intended..." message at the top of the window? If you do and you click Manage then click Trust does that solve the issue?

[kburtram]

I see in the original bug text that ADS is running in restricted mode, which would explain this behavior. I've updated the title to reflect this. We'll investigate how to improve this experience in Dec.

[kburtram]

This issue should be resolved in today's insider build. Please let us know if you still experience this problem with those builds. We're discussing potentially pushing this change as a hotfix due to the confusion/inconvenience caused by this bug.

[goudstad]

Please deploy the fix. I am having the same issue after upgrading to version 1.33.0. I don't see that I am in the restricted mode, however. Also, is there a way to downgrade to the previous version/release? If so, where can I find the previous release?

Windows 10

[Charles-Gagnon]

@goudstad Could you try out the latest insiders build and see if you're still seeing the issue there?

[goudstad]

I just upgraded to version 1.33.1. and I am no longer seeing the issue. Many thanks for fixing it.

[Charles-Gagnon]

Closing this since the hotfix with the fix has been released, if anyone else is still encountering issues let us know!