Monitoring Splunk

"Viewstate object not found" error while cloning a search

bbc
Engager

This is Splunk 5.0.1. Fresh install, i.e. not an upgrade from a previous version.

Sometimes, when trying to clone a search, I get an error like: "[HTTP 404] Viewstate object not found; view=* viewstate=foo" (and the clone fails).

What does this mean? Why does it happen? How can I resolve it?

I haven't yet tried to reduce this to a minimum set of reproducible steps, sorry.

Tags (3)

mdegann
Explorer

This usually means that there is no metadata for your Vewstate ID. The easiest way to fix this is to go into your savedsearches.conf and remove the

*vsid = **

Lines and do a https://127.0.0.1:8000/en-GB/debug/refresh. This will rebuild all the required VSID's, you could also take the alternate root and write them into your app/metadata/local.meta

sonicZ
Contributor

This method works, but I just migrated from Splunk4.3.2 to Splunk6.1, I have to do this for all users saved searches? Going to be a pain....

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...