Errors while creating HR case

shruthij
Tera Contributor

While creating the HR case am getting these errors

Error Message: Part of the query on change_task has been ignored because of read security rules on change_task.active
- Error Message: Part of the query on sc_task has been ignored because of read security rules on sc_task.active
- Error MessagePart of the query on sc_cat_item has been ignored because of read security rules on sc_cat_item.active
- Error MessagePart of the query on sc_cat_item has been ignored because of read security rules on sc_cat_item.no_search

3 REPLIES 3

Dnyaneshwaree
Mega Sage

Hello @shruthij ,

Your issue is similar to the issue i have just saw in other posts-  
https://www.servicenow.com/community/developer-forum/acl-error-after-upgrade/m-p/3001967#M1133620
https://www.servicenow.com/community/developer-forum/acl-error-after-upgrade/m-p/3001967#M1133620

So, Check your ACLs on that particular field. Update the changes if confirmed. And verify for upgrade issues.


Please accept my solution if it works for you and thumps up to mark it as helpful.
Thank you!!

Dnyaneshwaree Satpute
Tera Guru

HarishVardineni
Tera Contributor

We have faced similar issues after washington upgrade, we have checked (sys_search_source_list.do) records and noticed that there are  system created records with same table name and conditions with itil and admin read roles for one of the record. We tried to inactive one of the record that has itil and admin read roles but still error messages displaying. Once we have removed conditions like active = true or directly deleted the error record then issue resolved. 

HarishVardineni
Tera Contributor

@shruthij @Dnyaneshwaree 

 

I have faced similar issues after washington upgrade , we have checked (sys_search_source_list.do) records and noticed that there are  system created records with same table name and conditions with itil and admin read roles for one of the record. We tried to inactive one of the record that has itil and admin read roles but still error messages displaying. Once we have removed conditions like active = true or directly deleted the error record then issue resolved.