MS SQL driver: I can get connection to a DB and run SQL but I cannot see list of tables

[stephanemoulec]

I can connect to a SQL DB (Azure SQL instance), run code, but when I try to expand the connection to see the list of tables, I get the error "Request connection/GetChildrenForTreeItemRequest failed unexpectedly without providing any details."

I saw issues 640 and 642 but they apply to PostgreSQL. Could not use the solution.

My connection string: ` "sqltools.connections": [

    {
        "mssqlOptions": {
            "appName": "SQLTools",
            "useUTC": true,
            "encrypt": true
        },
        "previewLimit": 50,
        "server": "<my db server>",
        "port": 1433,
        "driver": "MSSQL",
        "name": "<my db name>",
        "database": "<my db name>",
        "username": "<user>",
        "password": "<password>"
    }
],`

[stephanemoulec]

Problem still exists. In most recent version (both VS Code and extension), I get message "Running the contributed command: 'sqltools.getChildrenForTreeItem' failed." when opening the tree

[anil-github-dev]

I've the same issue - using latest version 1.10.1 with the below properties. When expanding the connection getting the following error "Request connection/GetChildrenForTreeItemRequest failed unexpectedly without providing any details". I'm able to execute the SQLs without any issues after double clicking the connection.

{ "mssqlOptions": { "appName": "SQLTools", "useUTC": true, "encrypt": true }, "previewLimit": 50, "server": "", "port": 1433, "driver": "MSSQL", "name": "", "database": "", "username": "", "password": "" }

[Code4OSINT]

Running into the same issue/error, using PostgreSQL.

Database is visibly connected, running simple sql (create table) works fine. But cannot expand the connected db, error message keeps popping up:

Running the contributed command: 'sqltools.getChildrenForTreeItem' failed.

[magiruuvelvet]

I had the same issue today with a MariaDB database. Turned out the password was wrong, once I used the correct password the table tree was showing up in the sidebar. Really weird. I logged in as root user to the development database in case that matters.

The extension doesn't seem to handle invalid connections or wrong passwords correctly. When using some random IP address were no database is running I get all kinds of weird errors, instead of a useful one.

EDIT: The database showed up as successfully connected even though I used the wrong password.

[SADANANDKUMAR]

guys mine also have same problem

Running the contributed command: 'sqltools.getChildrenForTreeItem' failed.

[DustinWin]

guys mine also have same problem

Running the contributed command: 'sqltools.getChildrenForTreeItem' failed.

Same problem!

[MarcosBaungartner]

You need to click the plug icon (which is beside the name of the connection) to connect to the database, then it will ask for password.

[rangitoto72]

Same issue here:

Environment VSCode: February 2021 (version 1.54) SQL Tools: V 0.2.0 OS: OS11.2.3 ( Apple silicon)

Error: Running the contributed command: 'sqltools.getChildrenForTreeItem' failed.

Here is the connection, it is fine, as it has the green dot for connected as well as the option to disconnect.

Here is my select to return data (So it is connecting fine)

[paintmeyellow]

Same issue

Extension version: 0.23.0 VS Code version: Code 1.54.3 OS version: Linux x64 5.8.0-45-generic

[sajadshafi]

I also had the same issue as I switched to root user it worked fine. But logging in as another user doesn't work.

[filasik]

same problem, OS Windows 10

[Kaloyanes]

I have the same problem. OS: Windows 10

[nihirisuto]

Tested my connection credentials in dbeaver and this, and I'm getting the sqltools.getChildrenForTreeItem error for all but one connection. Was able to expand tables for one of them but the other 3 connections I'm trying aren't working.

[Pedram-Mirelmi]

same issue! i'm using MySQL server 8.0.23 on vscode 1.55.2 linux ubuntu 20.04 LTS it gives me an error with the message: "running the contributed command: 'sqltools.getChildrenForTreeItem' failed"

[LucasMarmo]

https://stackoverflow.com/questions/50093144/mysql-8-0-client-does-not-support-authentication-protocol-requested-by-server/50131831#50131831

Execute the following query in MYSQL Workbench

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'

Where root as your user localhost as your URL and password as your password

Then run this query to refresh privileges:

flush privileges;

Try connecting using node after you do so.

If that doesn't work, try it without @'localhost' part.

[rangitoto72]

https://stackoverflow.com/questions/50093144/mysql-8-0-client-does-not-support-authentication-protocol-requested-by-server/50131831#50131831

Execute the following query in MYSQL Workbench

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'

Where root as your user localhost as your URL and password as your password

Then run this query to refresh privileges:

flush privileges;

Try connecting using node after you do so.

If that doesn't work, try it without @'localhost' part.

Might work but as you can see, the initial query, as with my issue is for TSQL ( Microsoft SQL Server. NOT MySql ), so using root@localhost has nothing to do with it.

[psinnathurai]

Same Issue here.

[ecesar88]

Same here

[NathanSFon]

I was having the same problem. I decided to change the user to 'root' and in the password I left with ask when connecting, from that moment there was no error

[mdavinicius]

Same issue for me too :(

[KianoJ]

Me too I'm running MySQL on docker with WSL2 (Ubuntu) Latest version of VSCode and SQLTools

My docker-compose

version: '3'

services: 
    db:
        container_name: mysql
        image: mysql
        restart: always
        environment: 
            MYSQL_ROOT_PASSWORD: test123*

    
    phpmyadmin:
        image: phpmyadmin
        restart: always
        ports:
            - 8080:80
        environment:
            PMA_HOST: db
            PMA_USER: root
            PMA_PASSWORD: test123*

networks:
    default:
        external: true
        name: web

SQLTools connection

"sqltools.connections": [
    
        {
            "mysqlOptions": {
                "authProtocol": "default"
            },
            "previewLimit": 50,
            "server": "localhost",
            "port": 3306,
            "askForPassword": true,
            "driver": "MySQL",
            "name": "Inventaire",
            "database": "inventaire",
            "username": "root"
        }
    ],

[shinzoke]

Same thing here... would be Nice to have a decent fix or someone to point me into the right way... Using docker on wsl2

[RoneyThomas]

https://stackoverflow.com/questions/50093144/mysql-8-0-client-does-not-support-authentication-protocol-requested-by-server/50131831#50131831

Execute the following query in MYSQL Workbench

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'

Where root as your user localhost as your URL and password as your password

Then run this query to refresh privileges:

flush privileges;

Try connecting using node after you do so.

If that doesn't work, try it without @'localhost' part.

If anyone is having trouble with mysql 8.0 and above, use this and it will work.

[iwogar]

Hey, I'm not sure how MySQL got into this but the original issue was raised for MS SQL. Is this fix supposed to work for MS SQL too?

[RoneyThomas]

Hey, I'm not sure how MySQL got into this but the original issue was raised for MS SQL. Is this fix supposed to work for MS SQL too?

Yup

[psmatsinhe]

Hi, any explanation for this error beside having to downgrade!!!?

[huangjj27]

Hey, I'm not sure how MySQL got into this but the original issue was raised for MS SQL. Is this fix supposed to work for MS SQL too?

refer to Aidin's answer below that stackoverflow post.

[huangjj27]

Hi, any explanation for this error beside having to downgrade!!!?

refer to Aidin's answer below that stackoverflow post.

[huangjj27]

I think this issue can be fixed by adding support of authorization for caching_sha2_password, but as is mentioned in #101, this issue of MySQL version may be not fixed.

[willycotes]

in my case the problem was solved by changing the hostname "localhost" by the local ip "127.0.0.1"