Knowledge record not found error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2024 10:45 PM
Hi All,
We have recently upgraded our instance to xanadu, after we upgrade our instance we got a strange issue like whenever we search knowledge article in global search it is giving knowledge record not found error. Can please help me resolve.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2025 06:31 AM
Problem record PRB1830531 has been updated recently with targetted versions for fix: Zurich,Yokohama Patch 1,Xanadu Patch 6.
We've just took the nuclear approach and updated the prefix to affected KBs to fit within the standard number length which still works fine as we can't wait any longer for the fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2025 06:38 AM - edited 02-03-2025 07:16 AM
As usual we don't have access to view the PRB. Standard number lengths? Are you able to tell which KB's are affected thru a query as it seems random?
We have a mix of KB and KM prefixes. KM's are older and appear to be the affected ones.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2025 07:19 AM
If you raise a case with Now Support they'll link your ticket to the problem so you can view it.
The issue affetced knowledge articles which have numbers longer than 9 characters. For a couple of our knowledge bases we had 7 digits prefixed by 3 or 4 letters, giving total lengths of 10 and 11 respectively. Changing these prefixes to be 2 letters followed by 7 digits resolved for us, I believe reducing the number of digits to bring the total characters down to 9 would also have resolved however we didn't test this solution.
Example, KBA0012345 became KB0012345 and permalinks/global search then worked correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2025 02:12 PM
Hi,
We were facing the same issue and ServiceNow didn’t provide a direct workaround. However, we found our own solution. After upgrading to Patch 6 on the sub-instance, we took the code they applied as a fix in Patch 6.
The solution was implemented in the KBCommonSNC script include, but we cannot modify it due to security constraints. Instead, we added the necessary code to the KBCommon script include, which resolved the issue of not getting any search results when searching for KB articles from global search.
Script include : KBCommon
https://Instancename.service-now.com/sys_script_include.do?sys_id=39e84ab2d72121004792a1737e610306&s...
Function that added in this :
---------------------------------------------------------------------------------------------
Note: Make sure to remove this code once you upgrade with Patch 6.
Please mark this if it helpful.