azuredatastudio: Doesn't show databases, tables etc on some servers

  • Azure Data Studio Version:
Version: 1.23.0
Commit: d296b6397e0acfddc57e9085e736e084969cdaeb
Date: 2020-10-13T22:58:36.079Z
VS Code: 1.49.0
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0

Since upgrading to 1.23.0 (it worked in 1.22.1) I’m unable to see the databases, tables, or anything when connecting to some SQL servers. Screenshot: image

It works fine for the server I’m running in docker, but not the other one. I’m still able to execute queries on the server.

In renderer1.log I get the following error:

[2020-10-19 19:49:27.174] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2020-10-19 19:49:27.175] [renderer1] [error] Cannot read property 'isCloud' of null: TypeError: Cannot read property 'isCloud' of null
	at t.MssqlIconProvider.getConnectionIconId (/Applications/Azure Data Studio.app/Contents/Resources/app/extensions/mssql/dist/main.js:411:37866)
	at d.$getConnectionIconId (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:697:248)
	at g._doInvokeHandler (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:969:707)
	at g._invokeHandler (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:969:399)
	at g._receiveRequest (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:968:59)
	at g._receiveOneMessage (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:966:886)
	at /Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:965:34
	at l.fire (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:48:475)
	at v.fire (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:259:381)
	at /Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:1149:963
	at l.fire (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:48:475)
	at v.fire (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:259:381)
	at t.PersistentProtocol._receiveMessage (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:264:451)
	at /Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:261:489
	at l.fire (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:48:475)
	at p.acceptChunk (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:256:851)
	at /Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:256:203
	at Socket.t (/Applications/Azure Data Studio.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:266:54)
	at Socket.emit (events.js:223:5)
	at addChunk (_stream_readable.js:309:12)
	at readableAddChunk (_stream_readable.js:290:11)
	at Socket.Readable.push (_stream_readable.js:224:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)

I have had someone else test it as well with the same result

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 32 (8 by maintainers)

Most upvoted comments

@kburtram not sure these are duplicates. This problem started with 1.23.0 (it worked in 1.22.1) – the other issue #6450 was a problem way before that. Also this issue has no timeout or any other error. Actually the “Database Folder” is not even present. Appears to only affect on-prem SQL Server and not Azure.