Splunk Search

The lookup table '...' does not exist

marco_stiegeman
Engager

After installing the Windows App 5.0.2 on our splunk 5.0.3 i get these errors when doing a search:

The lookup table 'wmi_version_range_lookup' does not exist. It is referenced by configuration 'WMI:Version'.

The lookup table 'msdhcp_signature_lookup' does not exist. It is referenced by configuration 'DhcpSrvLog'.

I found this thread splunk answers but this didn't help ...

aelliott
Motivator

So I found that lookup tables are very picky. If they exist at an app level, they are only available for that app, no matter the permissions.
If you replace a lookup table, you must open the definition and automation and re-save them
One way to make them "less" picky is to put them at the system level, this makes them available in all apps. .. more info on that here: http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Addfieldsfromexternaldatasources

If you need to package the app, i found it necessary to add the lookup file/definition/automation to each app.

0 Karma

ShaneNewman
Motivator

I had to rerun the lookup search to create the lookup file manually after this. Once I did that, everything started working fine!

0 Karma

dprows
New Member

I have the same issue and the thread listed didn't help me either.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...