Splunk Search

Error: "The lookup table 'windows_action_lookup' does not exist. It is referenced by configuration 'ntsyslog:security'."

zliu
Splunk Employee
Splunk Employee

"The lookup table 'windows_action_lookup' does not exist. It is referenced by configuration 'ntsyslog:security'."

The lookup table 'windows_action_keywords_lookup' does not exist. It is referenced by configuration 'ntsyslog:security'.

added [lookups] export=system stanza in $splunk_home/etc/system/metadata/local.meta config file and restart splunkd, but it doesn't help 😞 unlike in this question: http://answers.splunk.com/questions/1716/error-in-lookup-command-the-lookup-table-test-lookup-does-n...

Found 'ntsyslog:security' at $SPLUNK_HOME/etc/apps/SKB-windows/local/props.conf: [ntsyslog:security] and $SPLUNK_HOME/etc/apps/SKB-windows/local/transforms.conf: FORMAT = sourcetype::ntsyslog:security

Tags (1)
0 Karma

the_wolverine
Champion

You should investigate whether you have a duplicate lookup table (by the same name) in an alternate location. If you do, make sure to keep the desired table that is referenced by the aforementioned configuration and delete the duplicate.

An easy way to find duplicate lookup tables is by going to the Manager >> Lookups >> Lookup Tables Files (in UI). You can delete the duplicate from this view without having to restart Splunk.

Get Updates on the Splunk Community!

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...