https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-is-there-a-following-error-in-lookup-command-quot-Lookups/m-p/394658#M4312 <P>Evidently this is well-known in support circles but not on the internet yet, so I am sharing my pain for your gain.<BR /> We just installed ES and everything was OK except for the following strangenesses:</P> <P>ES Notables are firing but not showing up on <CODE>Security Posture</CODE> ( <CODE>index=notables</CODE> shows plenty of action).<BR /> I am getting this error on several screens including <CODE>Audit</CODE> -&gt; <CODE>ES Configuration Health</CODE> (which will not run at all):</P> <PRE><CODE>Error in 'lookup' command: Lookups: The lookup table 'event_time_field=temp_time' does not exist or is not available. </CODE></PRE> <P>In ad-hoc search, click on the <CODE>v</CODE> and select the <CODE>Create Notable Event</CODE> action under <CODE>Event Action</CODE> menu and notice that there is no <CODE>Save</CODE> button.</P> <P>What is going on here?</P> Tue, 07 Aug 2018 19:13:30 GMT woodcock 2018-08-07T19:13:30Z https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-is-there-a-following-error-in-lookup-command-quot-Lookups/m-p/394658#M4312 <P>Evidently this is well-known in support circles but not on the internet yet, so I am sharing my pain for your gain.<BR /> We just installed ES and everything was OK except for the following strangenesses:</P> <P>ES Notables are firing but not showing up on <CODE>Security Posture</CODE> ( <CODE>index=notables</CODE> shows plenty of action).<BR /> I am getting this error on several screens including <CODE>Audit</CODE> -&gt; <CODE>ES Configuration Health</CODE> (which will not run at all):</P> <PRE><CODE>Error in 'lookup' command: Lookups: The lookup table 'event_time_field=temp_time' does not exist or is not available. </CODE></PRE> <P>In ad-hoc search, click on the <CODE>v</CODE> and select the <CODE>Create Notable Event</CODE> action under <CODE>Event Action</CODE> menu and notice that there is no <CODE>Save</CODE> button.</P> <P>What is going on here?</P> Tue, 07 Aug 2018 19:13:30 GMT https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-is-there-a-following-error-in-lookup-command-quot-Lookups/m-p/394658#M4312 woodcock 2018-08-07T19:13:30Z https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-is-there-a-following-error-in-lookup-command-quot-Lookups/m-p/394659#M4313 <P>Evidently these are all symptoms of running ES version 5.1 on version of Splunk core &lt; 7.1.0. Indeed, we are running v6.6.8. So now I need to decide if I should unisntall ES and install version 5.0 or upgrade core to v7.1.2. I am leaning towards the latter and hoping that I can avoid having to reinstall ES. I will report back with my findings after I get done.</P> Tue, 07 Aug 2018 19:15:49 GMT https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-is-there-a-following-error-in-lookup-command-quot-Lookups/m-p/394659#M4313 woodcock 2018-08-07T19:15:49Z https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-is-there-a-following-error-in-lookup-command-quot-Lookups/m-p/394660#M4314 <P>OK, I upgraded the cluster to v7.1.2 and all of the problems listed disappeared, so clearly that was the entire problem. The installer really should have complained and not allowed itself to proceed. At least now the symptoms are clearly documented here.</P> Tue, 07 Aug 2018 21:49:45 GMT https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-is-there-a-following-error-in-lookup-command-quot-Lookups/m-p/394660#M4314 woodcock 2018-08-07T21:49:45Z