Splunk has found 10 orphaned searches owned by 5 unique disabled users.Click to view the orphaned scheduled searches. Reassign them to a valid user to re-enable or alternatively disable the searches.

[hrithiktej]

Splunk has found 10 orphaned searches owned by 5 unique disabled users.Click to view the orphaned scheduled searches. Reassign them to a valid user to re-enable or alternatively disable the searches.

Please help i have followed several articles but not able to resolve this.

We have Splunk 6.6.3 and we started getting this message after we upgraded from 6.3.2 to 6.6.3

[graissaguel]

For unshared knowledge objects, you have to delete or move them from SPLUNK_DB/etc/users//local/*.conf (usually savedsearches.conf)

[richarddicaire]

Unfortunately, these objects cannot be found with Reassign Knowledge Objects.

Use the Reassign Knowledge Objects page in Settings
The Reassign Knowledge Objects page in Settings is the only orphaned knowledge object detection method that detects all knowledge objects (not just searches, reports, and alerts). However, it can only find knowledge objects that have been shared to the app or global levels.

So how to deal with objects that are not shared?

[elliotproebstel]

That message usually indicates that a saved search is owned by a user whose account has been disabled/deleted. The solution is to either delete the saved search (if it's no longer needed) or reassign the search to an active user. Here's some good guidance on that:
http://docs.splunk.com/Documentation/SplunkCloud/6.6.3/Knowledge/Resolveorphanedsearches