Alerting

Getting a cannot find viewstate when disabling alerts

lanilim16
Explorer

I'm a admin user and when I try to disable any alert

I get an error similar to the one blelow
In handler 'savedsearch': Cannot find viewstate with vsid="gle4xmxd"

Tags (3)
0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

Sounds like a broken link from times gone by... go to that savedsearches.conf and remove the line vsid=gle4xmxd from that saved search's stanza.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

Sounds like a broken link from times gone by... go to that savedsearches.conf and remove the line vsid=gle4xmxd from that saved search's stanza.

martin_mueller
SplunkTrust
SplunkTrust

After editing .conf files manually you will need to either restart splunk or hit http://splunk_host:port/debug/refresh?entity=saved/search to tell splunk about the changed file.

There will be no impact because the viewstate apparently doesn't exist any more. Can't lose something that's already gone.

0 Karma

lanilim16
Explorer

awesome thanks, this actually worked the URL is http://splunk_host:port/debug/refresh?entity=admin/savedsearch to do a refresh without restart

0 Karma

lanilim16
Explorer

I already removed this from savedsearches.conf beforehand and still get the same error, am I supposed to restart the app for this to take effect? Further to this all alerts are actually resulting to this error message, so if I remove this, will there be any impact?

0 Karma
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...