Splunk Enterprise Security

migration

SN1
Path Finder

Hello recently I moved ES app from one sh to another non clustered sh . after that this error is coming

Error in 'DispatchManager': The user 'admin' does not have sufficient search privileges

0 Karma

livehybrid
SplunkTrust
SplunkTrust

Hi @SN1 

Did you use a user-seed.conf when setting up the new SH? And/Or did you create an admin user that isnt called "admin"?

It sounds like your admin user does not exist, but there are searches owned by the "admin" user.

To resolve change "owner = admin" and update to a user which exists (ideally a service user) in the default (or local).meta files in all apps on your SH ($SPLUNK_HOME/etc/apps/<appName>/metadata/*.meta

Also check out https://community.splunk.com/t5/Reporting/Why-am-I-getting-error-quot-DispatchManager-The-user-admin...

Please let me know how you get on and consider accepting this answer or adding karma this answer if it has helped.
Regards

Will

0 Karma

SN1
Path Finder

so i removed this stanza from default.meta file
[savedsearches]
owner = admin

and it started working how ?

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...