Error - The requested database is currently being modified by another user. please try again later.
The message appeared yesterday afternoon on some screens in the capsule other screens in the same capsule work without the error message.
I have restarted the service but this did not resolve the issue.
What can we do to resolve this?
Answers
-
Hi Olu,
I have been getting this error message when there is a problem with the screen selection, it might be due to a dynamic selection for your screens. Disable the selection for an entity and then see if that helped, like that you should be able to find out which entity selection is causing the issue, if that is the problem.
Cheers,
Daniel0 -
Hi Daniel,
Thanks for suggestions, but I cannot even access the screen selection function, I
get the same error message.0 -
Hi,
in my experience this is a problem with the screen selection - and more specifically a selection on an entity which does not exist in the current database.
This can happen when you switch a capsule to a different database or a different version of your database where this entity does not exist. The screen tries to apply the selection and it results in this error message.
Possible solution: change the capsule back to the "correct" database and remove the problematic selection -> save the screen.
BR
Sebastian
1 -
I have not changed the database or created a new entity
0 -
Do you have a dynamic selection on an empty Cube? If so i would check the database to see if there is an empty cube. If you want to change the screen selection you can navigate to the screen using a procedure with remove all and apply selection to screen.
5 -
I had this several times suddenly happening from one day to another when there was a selection on an entity where the tree was not consistent. Can be somewhere in the tree and has not to be the specific entity that is used for selection
Check your relationships especially top down to see if you have parent items without child items in your trees.
Regards
Susanne
5 -
I agree with Susanne Rossow
when i had this issue, 99% of times it was related to missing relationships: bottom-up or top-down.
pay attention also to the time-tree relationships.regards,
federico
0
