- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā05-13-2025 08:31 AM
Part of the query on sys_user has been ignored because of insufficient access for 'query_range' operation on sys_user_grmember.user
So we recently got our May security maintenance done and I am having an issue with the above error
I have created a new ACL for this but it is still erroring I did raise a ticket but wasn't very helpful and the KB's don't really advise how to resolve this
I am not sure what I am doing wrong I did have one related to a query match which i resolved but this query range one is stumping me
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā05-14-2025 03:43 AM
So it appears me updating these ACL's to change from public and also changing the security attribute to local seems to have fixed the error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā05-15-2025 01:04 AM
Hi, I'm experiencing the same issue in my instance when viewing reports that contain custom fields. The query range ACL includes the scrum_user role, which most users have, but the reports still aren't displayed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā05-16-2025 03:21 AM
@MatteoMazz have you tried to set the security attributes to local and seen if that fixes it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā06-03-2025 01:22 PM
It seems there is an article out there where they have explained the Securty patch. Hope this may help people who faces the issue.
https://www.ikconsulting.com/post/understanding-servicenow-s-may-2025-query-range-acl-update-what-yo...