- Find Answers
- :
- Splunk Administration
- :
- Admin Other
- :
- Installation
- :
- Cannot delete, move, or clone Saved Searches after...
- 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 just upgraded to Splunk 5.0 and all of our upgraded saved searches and reports can no longer be deleted or moved via SplunkWeb. Why do we have to remove or move them manually from the server?
We also cannot clone our existing saved searches or reports (as an admin we receive: `Encountered the following error while trying to clone: [HTTP 404] Viewstate object not found; view= viewstate=oflqsidy`*).
If we create a new saved search or report - we have access to delete/move and can properly clone without any issues. This seems to be an upgrade issue.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Turns out that this issue has nothing to do with upgrading - I couldn't delete or move because these searches were imported via an application package (*.spl) and were located in the /default directory instead of the /local directory. Once I moved the saved search config from the /default path to /local/savedsearches.conf I was then able to delete them via Splunk Web - this is just my lack of understanding of what is user-manageable versus system-manageable.
The clone problem exists because the Viewstate ID (vsid) wasn't present in the viewstates.conf. You can either add an empty viewstate or copy the source state by doing the following:
viewstates.conf
#...
[*:oflqsidy]
#...
Once I added the vsid to the viewstates.conf in the /local path, I was able to properly clone.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
another option is to simply go into the savedsearches.conf for the search in question and delete the vsid attribute.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Turns out that this issue has nothing to do with upgrading - I couldn't delete or move because these searches were imported via an application package (*.spl) and were located in the /default directory instead of the /local directory. Once I moved the saved search config from the /default path to /local/savedsearches.conf I was then able to delete them via Splunk Web - this is just my lack of understanding of what is user-manageable versus system-manageable.
The clone problem exists because the Viewstate ID (vsid) wasn't present in the viewstates.conf. You can either add an empty viewstate or copy the source state by doing the following:
viewstates.conf
#...
[*:oflqsidy]
#...
Once I added the vsid to the viewstates.conf in the /local path, I was able to properly clone.
Enterprise Security Content Update (ESCU) | New Releases
Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?
Index This | What are the 12 Days of Splunk-mas?
