All Apps and Add-ons

Could not load lookup=LOOKUP-user_account_control_property

alonsocaio
Contributor

After updating Splunk_TA_Windows to version 6.0.0, I am getting error messages on every search I run.

[INDEXER 1] Could not load lookup=LOOKUP-user_account_control_property
[INDEXER 2] Could not load lookup=LOOKUP-user_account_control_property
[INDEXER 3] Could not load lookup=LOOKUP-user_account_control_property
[HEAVY FORWARDER] Could not load lookup=LOOKUP-user_account_control_property

All my instances (SH, Indexers and HF) are using the same version of Splunk_TA_Windows (6.0.0) and Splunk Enterprise (7.2.6). I am able to find this lookup in the Splunk_TA_Windows folder, using CLI, but It looks like Splunk is not finding It in any of my instances. When I disable this lookup in my SH I still get error messages.

Any tips on how to solve this issue? Does anyone knows what causes this error messages?

lakshman239
Influencer

Have you looked at the transforms.conf related to those lookup definitions and also permissions (in default.meta/local.meta) or Via GUI? if they are available, they got to have export=system permissions.

alonsocaio
Contributor

Hi

In my default/transforms.conf I have this:

[user_account_control_property]
external_cmd = user_account_control_property.py userAccountControl userAccountPropertyFlag
external_type = python
fields_list = userAccountControl,userAccountPropertyFlag

And the python script is located ate splunk_ta_windows/bin.

0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...