Getting error "Syntax Error or Access Rule Violation detected by database (conn=177111)"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2024 04:20 AM - edited ‎10-01-2024 05:04 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2024 04:24 AM
@souvikmallick Please refer to this post https://www.servicenow.com/community/developer-forum/syntax-error-or-access-rule-violation-detected-... similar issue was reported here.
In a nut shell, you need to check if there are any ACLs, reports defined on the deleted table which still exists.
Create a support case with ServiceNow if none of the suggestion work for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2024 04:37 AM
When a table is deleted, the associated ACLs are also deleted. So i am assuming ACLs are not the issue, I have also verified that there are no associated reports. I deleted this table previously and also restored it and did not see this issue back then.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2024 04:42 AM
There must be something which was referring to this table which got unlinked when you deleted the table. Since you restored the table back everything went back to how it was earlier.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2024 05:40 AM
The error suggests that there may still be references to the deleted table in your instance.
Look for any active references to the deleted table in other tables, such as BR, Script include, workflows, scheduled jobs.
Sometimes, cached information can cause issues. Clear your instance cache.
If there were any records in the deleted table that were being referenced elsewhere (like in another table), those references may need to be removed or updated.
If above options not helps then check the System Logs under System Logs > System Log > All to see if there are more details about what is triggering the error.
thank you
Rajesh