Robomongo: RoboMongo 0.9.0 : Script executed successfully, but there is no results to show

[tishakariya]

while executing command
db.getCollection('collectioname').find({});
Output shown is:
Script executed successfully, but there is no results to show
Where as there are (3000) documents in the collection, is there any issue??
RoboMongo Version : 0.9.0 Final
OS: Windows 7

[juliashibalko]

Hi @tishakariya, thanks for reporting the issue!
Could you please try this solution, it solved a lot of problems in the past: https://github.com/paralect/robomongo/issues/1106#issuecomment-230258348

Please let us know how it went.

[tishakariya]

Hey, Thanks for your reply @juliashibalko, it did not work with that,
still the same error.
The server i am trying to access is a Cloud server running on MongoDB 3.4.0.

[juliashibalko]

@tishakariya thanks for details. Could you please share more details to help us with reproducing:

1. Are you using connection with SSL, SSH or Authentication (if yes, is this admin)?
2. If it possible, could you tell us more about documents stored in DB? Do they have big size?
   Thanks in advance!

[timkarnold]

Seeing this randomly as well. Seems influenced network latency, as it was occurring more frequently when tethered with a slow data connection. Re-attempting the query usually return results after one or more additional attempts.

1) Authentication as admin, no SSL
2) Seems to happen on both large and small size document queries

[Getz85]

Same issue here. It looks like the message is displayed only on time-consuming request (ie > 5 seconds).

For information, I tried with all 0.9.0-RCX version since the RC6, and the problem appeared with the 0.9.0-RC8 release.

So I suggest to other user with that problem to switch temporarily to RC7 version.

[juliashibalko]

Hello guys!
@tishakariya could you please check issue with Robo3T v.1.1 and share results if possible? We implemented support of 3.4 MongoDB and I hope the issue won't be reproduced under this version. Please see new release here https://robomongo.org/download.

@timkarnold @Getz85 could you please try this solution, it solved a lot of problems in the past (increase shell timeout in Options > Change Shell Timeout: https://github.com/Studio3T/robomongo/issues/1106#issuecomment-310334178. Check blog http://blog.robomongo.org/robomongo-is-robo-3t/#4a. Please let us know how it went.

[andreeaflazar]

I have the same problem here, my classmates have a result but I get this message. I'm using Mongo 4.1.4 and the latest version of Mongodb. I don't know how to fix it...