Robomongo: Find command not yet implemented

Created on 5 Sep 2019 · 12Comments · Source: Studio3T/robomongo

Just installed Robo T3 on windows 10 and trying to edit an existing document gives me this error and the changes won't save.

Failed to load documents.

Error:
Find command not yet implemented

Source

JohanTh

👍10

All 12 comments

Same error here. Windows 10 and Robo 3T 1.3.1

katmandu25 on 10 Oct 2019

Also getting this on Ubuntu 18.04.3 LTS with Robo 3T 1.3.1

JohanTh on 12 Nov 2019

👍1

I'm getting the same error on Ubuntu 16.04 LTS with Robo 3T 1.3.1.

jb-berthet on 11 Dec 2019

the same error on macos 10.14.6 and robo 3t 1.3.1

zhang-yupeng on 19 Dec 2019

This appears to be an issue with Mongo 3.0.x servers, 3.2.x is unaffected. Robo 3T 1.2 did not have this problem.

davemorrissey on 26 Feb 2020

👍1

I'm also on Robo 3T 1.3.1 experiencing this with a Mongo 3.0.x server, I'm on MacOS 10.14.6.

wraithan on 12 Mar 2020

Any get a solution to this? I´m also Robo 3T 1.3.1 and 10.14.6

sebafra on 12 Apr 2020

Hi all, thanks for reporting the problem. Seems that the problem is seen only with MongoDB 3.0.
I suspect, this is highly likely due to mongo version upgrade from 3.4 to 4.0.5 in Robo 3T 1.3.
See: https://github.com/Studio3T/robomongo/blob/master/CHANGELOG#L8

Robo directly depends on the mongo code, but still, we will check if something can be done to fix this problem.

Is there anyone who has this problem with a different MongoDB version than 3.0?

simsekgokhan on 22 Apr 2020

I have the same error with mongodb version 3.0.15. when attempting to page the results using the arrows in the results grid. Windows 10 here with robo 3t 1.3.1

davyarris on 22 Jun 2020

👍1

We have done some investigation/debugging and seems like a driver compatibility issue. The error is coming from MongoDB server 3.0.

And there is also related commit, seems like they have fixed it in version r3.1.1:
https://github.com/mongodb/mongo/commit/4049c8328c98d8eb2b84fffca43ff4904e936909#diff-7a8f242c8081e0cf398db7ee6608f3cbL142

So, for now the workaround solution to work with MongoDB 3.0 seems to be using Robo 3T 1.2 or upgrading your MongoDB server version.

simsekgokhan on 22 Jun 2020

👍1

Thanks simsekgokhan. That does make sense. We can upgrade to a newer version so that is good. Not so good for people that cannot.

davyarris on 25 Jun 2020

👍1

This doesn't seem to be fixed on the latest Robo 3T 1.4.1 release as well. This is a bit difficult to use since every time a document is edited this error is shown and we need to restart Robo 3T (mongod server version v3.0.15).
Do you have a link to Robo3T 1.2 versions?