ERROR: not authorized to execute c…610139008696321 } Timestamp(1560445148)
Cannot Reproduce
good afternoon,this error is shown frequently when I make queries, the temporary solution I found is to close "mongobooster" and return
please your kind support
The same problem 
Thanks for opening your first issue here! If you're reporting a
bug, please make sure you include steps to reproduce it.
Thanks for opening your first issue here! If you're reporting a
bug, please make sure you include steps to reproduce it.
NoSQLBooster Version: 5.1.8
Operating System (Windows / Mac / Ubuntu): Windows 10 PRO
Expected Behavior: Use the tool without problems.
Actual Behavior: Every 2 minutes the application must be closed, since when executing a sentence (even if it is simple, eg: a SELECT TOP 5 *) an error message is displayed
How to Reproduce:
1. Login to the NoSQLBooster tooling
2. Start with the creation of a sentence
3. While the time is less than 2min, it can run without problems
4. If the time is longer or reaches 2 min, an error message is displayed
Screenshots:
NoSQLBooster Version: 5.1.8
Operating System (Windows / Mac / Ubuntu): Windows 10 PRO
Expected Behavior: Use the tool without problems.
Actual Behavior: Every 2 minutes the application must be closed, since when executing a sentence (even if it is simple, eg: a SELECT TOP 5 *) an error message is displayed
How to Reproduce:
1. Login to the NoSQLBooster tooling
2. Start with the creation of a sentence
3. While the time is less than 2min, it can run without problems
4. If the time is longer or reaches 2 min, an error message is displayed
Screenshots:
According to your steps, I still can't reproduce the problem. Can you describe your steps in detail to allow me to reproduce the problem locally?
Unless I can reproduce the problem locally or allow me to temporarily visit your MongoDB Server, it is difficult for me to solve the problem by guessing.
According to your steps, I still can't reproduce the problem. Can you describe your steps in detail to allow me to reproduce the problem locally?
Unless I can reproduce the problem locally or allow me to temporarily visit your MongoDB Server, it is difficult for me to solve the problem by guessing.
Replies have been locked on this page!