HI, I got an error when used robo3T(1.2) to connect mongodb(3.4.1) on window 7:
failed to load list of databases, and the error detail is "Failed to execute "listdatabases" command. ".
But access control is not enabled for my mongo server. How can i solve this problem?
Here is the mongodb server log:
[thread1] connection accepted from 127.0.0.1:63516 #3487 (28 connections now open)
[conn3487] received client metadata from 127.0.0.1:63516 conn3487: { application: { name: "robo3t" }, driver: { name: "MongoDB Internal Client", version: "3.4.3-10-g865d2fb" }, os: { type: "Windows", name: "Microsoft Windows 7", architecture: "x86_64", version: "6.1 SP1 (build 7601)" } }
[conn3487] command admin.$cmd appName: "robo3t" command: listDatabases { listDatabases: 1, nameOnly: true } numYields:0 reslen:18812 locks:{ Global: { acquireCount: { r: 448 } }, Database: { acquireCount: { r: 223 } } } protocol:op_command 12014ms
[conn3487] end connection 127.0.0.1:63516 (28 connections now open)
Same happening here. Possibly something wrong with our data folder. Can anyone help?
Hi @watoua, @GCSBOSS and all, thanks for reporting the problem.
Can you share the followings for further investigation please?
// Example for Windows
E:\>mongo
MongoDB shell version v3.4.18
connecting to: mongodb://127.0.0.1:27017
MongoDB server version: 3.4.18
Welcome to the MongoDB shell.
> db.adminCommand( { listDatabases: 1 } )
{
"databases" : [
...
}
Meantime, I suggest the following actions:
Hello. You need to go to Manage Connections > Edit > Authentication. Fill in the details there. That should work like magic.
Hello guy! I am trying do that. error again
We still need more details for further investigation.
Meantime, you can try the beta. Feel free to open the ticket if you find problem again.
Closing due to insufficient information about problem.
Robo 3T 1.3 Beta
https://github.com/Studio3T/robomongo/releases/tag/v1.3.0-beta
Can confirm, latest beta fixes this issue.
Thanks a lot for the feedback @Qix
@simsekgokhan This is still an issue: Robo3t cant handle when there are zero databases on the server:
If i run this in the shell:
rs0:PRIMARY> db.adminCommand( { listDatabases: 1 } )
{ "databases" : [ ], "totalSize" : 0, "ok" : 1 }
Robo3t will result in: Failed to execute "listdatabases" command
Running version 1.3
I just had this issue with 1.2 connecting to a new mongo 4.2
It's fixed when using robo3t version 1.3, which supports newer version of mongo
Beta fixed it for me as well. Thanks!
I have Robo 3T 1.3.1. I still have this problem.
For me Have updated my Robo 3T version to 1.3.1 and hence I use it on local environment with out username and password, even after new installation, for some reason Perform authentication was enabled. I have to disable it. And it worked for me.

Worked for me now. The problem was: It can't connect if there are no databases to list. I had to create a database and a collection for it. Error message is misleading, but once you create a database and a collection, it works.
same problem
@FrancescoSaverioZuppichini
Are you running a local version?
try to login to the server and create a db and insert something in to the collection.
Also check the Robo 3T client Version.
1.3.1 works fine without auth and list of DB is possible.
1.3.1 works for me.
I had the same problem with version 1.2.1, works with 1.3.1
just install latest version of 3t
Same issue with 1.2 version, but 1.3.1 works on my side too.
You'll need to use 1.3 version! :)

I am using the latest version but I can not connect to MongoDB at local host
You'll need to upgrade mongodb to the last version, so you can to connect in your local database.
Actully I am using the latest version and I managed to connect to database after filling in the authentication field while creating a new connection. I had no issue yesterday but today I receive the error which can be seen on the picture. I could not figure out the reason???

Just downloaded the latest 1.3.1 and ran it. It's working fine now.
Thank you very much for the information.
14 Åžub 2020 Cum, saat 02:15 tarihinde Lisaiceland notifications@github.com
şunu yazdı:
Just downloaded the latest 1.3.1 and ran it. It's working fine now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Studio3T/robomongo/issues/1566?email_source=notifications&email_token=ANEJLEVQJGK6NKVI3I2AU7DRCXWDJA5CNFSM4FMZITO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELXGXXY#issuecomment-586050527,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANEJLETQ3HEWF2OIKYJITUDRCXWDJANCNFSM4FMZITOQ
.
We still need more details for further investigation.
Meantime, you can try the beta. Feel free to open the ticket if you find problem again.
Closing due to insufficient information about problem.Robo 3T 1.3 Beta
https://github.com/Studio3T/robomongo/releases/tag/v1.3.0-beta
I just updated robo3t from version 1.2 to version 1.3 and it worked with mongodb new version (4+)
I was also facing the same issue.
So i updated my robo3t from 1.2 to 1.3 with the latest mongodb version.
And it is working perfectly now
It seems there were two issues here. I tried with the latest 1.3.1 and had the issue. As soon as I created a DB through Azure Cosmos DB portal, it worked.

Just upgraded to Robo 3T for Mac 1.4 and now getting this.
Because you need to add authentication and enable the checkbox for manually specify visible databases
Most helpful comment
I just had this issue with 1.2 connecting to a new mongo 4.2
It's fixed when using robo3t version 1.3, which supports newer version of mongo