- Apps and Add-ons
- :
- All Apps and Add-ons
- :
- iSeries/as400 app lookup table error after upgradi...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We upgraded Splunk yesterday from 4.2.3 to 5.0.2 and have consistently received the error "[server name] The lookup table 'jrn _ detail _ lookup' does not exist. It is referenced by configuration 'dspjrn:5'.
The error appears within any apps that I go into (i.e. Cisco, Windows, iSeries). I have tried to upgrade the iSeries app, but the error still appears. Any suggestions? Thanks!
*Update...we recently upgraded to 5.0.2.2 after having other issues with the system. The error still appears even though I can see the lookup table in the app config.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To fix this issue, edit $SPLUNK_HOME/etc/apps/iseries/metadata/local.meta
and, edit following:
[lookups]
export = system
This worked for me.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To fix this issue, edit $SPLUNK_HOME/etc/apps/iseries/metadata/local.meta
and, edit following:
[lookups]
export = system
This worked for me.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you! It appears to be working for me as well.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
BTW this is an iseries lookup issue. I don't think the dspjrn lookup is in cisco or anything else. I think this question would be better off if it was titled iseries lookup or as400 app related.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Me three, haven't found a solution to this as well. Perhaps the author can chime in.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We still have not found an answer to this solution. I have tried other fixes from the 4.1 upgrade however it did not fix the issue. If I find a solution that works I will make sure to post it in here since it seems to be a problem with multiple users.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Got the same error since upgraded to 5.0.2.
Still looking...
Introducing the 2024 SplunkTrust!
Introducing the 2024 Splunk MVPs!
Splunk Custom Visualizations App End of Life
