Issue with data store entity

I think,You do not have access to Data store entity
Go to -> System tab-> Data Store->select your Data store and check security.

Checked security settings. I have given Administrator access to a group and I am member of that group.

Is the a!queryEntity running as part of a rule in a process or form, and therefore not as yourself, or are you running it in isolation. Also, if you have a constant for the data entity, have you checked it is set correctly?

If a!queryEntity is used in a tempo form (as a task) and basic user is trying to access that form:
1) Need to check whether security privilege is given to basic user on the process model, in which this form is used ?
2) Need to check whether security privilege is given to basic user on data store ?

Always remember that
"Security on folders,rules and constants does not impact end users ability to run a process or view an interface that refers this rules and constants, the security simply determines who has access to rules and constants in the folder in a designer interface"

@pallavis It might be worth going through philb's suggestion. I suspect there is a problem with the constant. Are you able to attach the logs?

i verified security settings.. seem to be good. Also in logs we observed one wokpoller issue.ERROR com.appiancorp.ra.workpoller.WorkPoller - Could not obtain 3 thread(s) after 23390000 attempts in work poller
2015-05-20 06:31:22,209 [Appian WorkPoller - 1 [Notifications]] ERROR com.appiancorp.ra.workpoller.WorkPoller - Could not obtain 3 thread(s) after 23400000 attempts in work poller
2015-05-20 06:31:22,659 [Appian WorkPoller - 0 [ProcessDesign]] ERROR com.appiancorp.ra.workpoller.WorkPoller - Could not obtain 3 thread(s) after 23400000 attempts in work poller
Does this issue causing problem in any ways?

@pallavis AFAIK the content of logs you have described here might not be related to the issue you are seeing with a!queryEntity() (Again let's see if anyone comes back on this). It would be worth if you could attach the logs that were generated at the time when a!queryEntity() has been run and failed.

@All, the issue got resolved after server restart..

we are facing the same issue with one of our CDT on a Data store and we got this issue only 2 times on recent days. Nothing has been changed on the environment for a while. not sure why it happened only twice suddenly. Can any one suggest a better solution and it happened on Production environment.

@ganeshbabuj Would you be able to attach logs that were generated at the time when query rule failed? Also, I would suggest elaborating the way the query rule is being invoked(i.e. is it invoked in a process/interface/in isolation etc).

If you are confident that nothing has been changed and the implementation is going well and failing in rarest of the rare cases, it might be worth raising a support case.