Splunk Enterprise

Cannot re-assign ownership of phantom orphaned searches

DaClyde
Contributor

Everyone on our project recently got new CAC cards, and the new cards have a longer ID number on them than before.  As a result, all of our account IDs changed which resulted in almost all of our searches being orphaned.

I found how to go to the All Configurations and use the Reassign Knowledge Objects to fix them, but we are now left with a recurring system alert for 5 orphaned searches that are still tied to my old ID number.  If I try to filter the Reassign Knowledge Objects page for Orphaned searches, these 5 do not show up.

When I go look at the actual searches, they have all been successfully re-assigned and show my new ID number, but the alert persists.  

How can I clear this persistent false positive Orphaned Search alert?

Labels (2)
Tags (1)
0 Karma

scelikok
SplunkTrust
SplunkTrust

Hi @DaClyde,

I had the same problem before, if you have admin rights, you can try adding old ID number as local user to Splunk. You should be able to see those searches, change the owner to your new ID and delete old ID local user.

If this reply helps you an upvote and "Accept as Solution" is appreciated.
0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

 (view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...