mtxr / vscode-sqltools

Database management for VSCode
https://vscode-sqltools.mteixeira.dev?utm_source=github&utm_medium=homepage-link
MIT License
1.44k stars 291 forks source link

Unable to see connection tree #878

Open MatCast opened 2 years ago

MatCast commented 2 years ago

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 image

Desktop (please complete the following information):

tarekahf commented 2 years ago

I have the same problem. Any resolution found?

tkekawa3712 commented 2 years ago

Any resolution?

gjsjohnmurray commented 1 year ago

After connecting are you able to run this query?

SELECT * FROM INFORMATION_SCHEMA.TABLES

If so, does this list schemas and tables?

git1453 commented 1 year ago

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

SELECT * FROM INFORMATION_SCHEMA.TABLES

Then

image
gjsjohnmurray commented 1 year ago

@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 commented 1 year ago

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

SELECT * FROM INFORMATION_SCHEMA.TABLES

Then I get this image

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 commented 1 year ago

@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 commented 1 year ago

@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 commented 1 year ago

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

tarekahf commented 1 year ago

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

How to increase the timeout?

SecondSite-web commented 1 year ago

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

jasonedokpa commented 1 year ago

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

shalevku commented 4 months ago

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 commented 2 months ago

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

fzhem commented 1 month ago

Related to #710