Unable to see connection tree

[MatCast]

Describe the bug
When clicking on the left arrow on an active connection i get the following error and the connection tree is not shown:
Request connection/GetChildrenForTreeItemRequest failed unexpectedly without providing any details.

After the error appeared once it does not show up again upon re-clicking on the arrow but the connection tree still does not diplay.

I can run queries on the DB normally.

Expected behavior
The connection tree is shown when clicking on the connection arrow.

Screenshots

Desktop (please complete the following information):

• SQLTools Version v0.23.0
• VSCode Version: 1.62.1
• OS: Windows 10
• Driver:
  • MSSQL/Azure
• Database version: Microsoft Azure SQL Data Warehouse - 10.0.13655.0

[tarekahf]

I have the same problem. Any resolution found?

[tkekawa3712]

Any resolution?

[gjsjohnmurray]

After connecting are you able to run this query?

SELECT * FROM INFORMATION_SCHEMA.TABLES

If so, does this list schemas and tables?

[git1453]

I have the same problem.
And when I want to run this query

SELECT * FROM INFORMATION_SCHEMA.TABLES

Then

[gjsjohnmurray]

@git1453 please confirm which driver you are using, and which versions of the driver and main extension.

Does the CONSOLE button give any more information?

And if you right-click on your connection in the SQLTools view, choose "Edit Connection", then press "TEST CONNECTION" does this succeed?

[packyzbq]

@gjsjohnmurray
I have the same problem.
And when I run the query

SELECT * FROM INFORMATION_SCHEMA.TABLES

Then I get this

The console output is

Connection is closed.

By the way,
SQLTools Version v0.26.0
SQLTools Microsoft SQL Server/Azure: v0.3.0
VSCode Version: 1.73.1
OS: Windows 10
Driver:
MSSQL/Azure
Database version: Microsoft SQLServer 2014

[gjsjohnmurray]

@packyzbq I don't have access to an instance of SQL Server 2014 to test against.

If you take SQLTools out of the equation by opening a native MSSQL command shell on that server and database, using the same userid as your SQLTools connection specifies, does that statement work?

[packyzbq]

@packyzbq I don't have access to an instance of SQL Server 2014 to test against.

If you take SQLTools out of the equation by opening a native MSSQL command shell on that server and database, using the same userid as your SQLTools connection specifies, does that statement work?

@gjsjohnmurray
YES. And I also tried running this statement on both DataGrip and SQL Server extension for Visual Studio Code with the same userid, and it worked fine.

[pallapo]

try to increase connection timeout, for me 50000 worked fine.

[tarekahf]

try to increase connection timeout, for me 50000 worked fine.

How to increase the timeout?

[SecondSite-web]

I had the same problem now. Solved it by unchecking the 'useUTC' option in VSCode - SQL Tools Settings in the connection settings

[jasonedokpa]

I tried the same, and sadly, that did not work for me.

[shalevku]

Same problem here, connection tree doesn't expand but queries work including the query that gjsjohnmurray suggested to try:

SELECT * FROM INFORMATION_SCHEMA.TABLES

[csubhodeep]

Hello all, do we have any workaround for this one?

[fzhem]

Related to #710

[fzhem]

@csubhodeep The sisue occurs due to how list of databases is retrieved. I've fixed this issue in my fork:

https://marketplace.visualstudio.com/items?itemName=fzhem.sqltools-driver-mssql-commver

[Lument-AndrewExley]

Can concur same experience with "Request connection/GetChildrenForTreeItemRequest failed unexpectedly without providing any details."

@fzhem Thanks for identifying and offering a fork, unfortunately, being on Apple Silicon, it isn't supported for me.

[fzhem]

Can concur same experience with "Request connection/GetChildrenForTreeItemRequest failed unexpectedly without providing any details."

@fzhem Thanks for identifying and offering a fork, unfortunately, being on Apple Silicon, it isn't supported for me.

@Lument-AndrewExley The fork currently supports the msnodesqlv8 driver, which has limited platform compatibility. Given sufficient interest, I may make it universal by disabling msnodesqlv8 on unsupported platforms. This will take time alongside other projects and day-to-day work, but I can create a pull request to address the issue in the official driver in the meantime.