<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: User has left the company, now getting &amp;quot;Could not find user:&amp;quot; errors in Security</title>
    <link>https://community.splunk.com/t5/Security/User-has-left-the-company-now-getting-quot-Could-not-find-user/m-p/75984#M2525</link>
    <description>&lt;P&gt;Make sure the users not in any meta files either.  If you're on a linux machine I'd do the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;grep -r "username" $SPLUNK_HOME
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That'll find all instances of the user name in any configuration files.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Feb 2012 08:07:39 GMT</pubDate>
    <dc:creator>Brian_Osburn</dc:creator>
    <dc:date>2012-02-22T08:07:39Z</dc:date>
    <item>
      <title>User has left the company, now getting "Could not find user:" errors</title>
      <link>https://community.splunk.com/t5/Security/User-has-left-the-company-now-getting-quot-Could-not-find-user/m-p/75982#M2523</link>
      <description>&lt;P&gt;I've had a few users leave the company now that have had saved searches.  Removing the $splunk_home/etc/users/&lt;USER_NAME&gt; directory doesn't resolve the errors.&lt;/USER_NAME&gt;&lt;/P&gt;

&lt;P&gt;If I search for files that contain the login name, I find the following example entry for "tuser"q:&lt;BR /&gt;
etc/apps/search/local/viewstates.conf:&lt;BR /&gt;
[viewstates/flashtimeline%3Agu5s5mv8]&lt;BR /&gt;
owner = tuser&lt;BR /&gt;
version = 4.2.3&lt;BR /&gt;
export = system&lt;/P&gt;

&lt;P&gt;Is it safe to remove these entries?  Is there a better way to remove terminated users?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 11:25:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/User-has-left-the-company-now-getting-quot-Could-not-find-user/m-p/75982#M2523</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2020-09-28T11:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: User has left the company, now getting "Could not find user:" errors</title>
      <link>https://community.splunk.com/t5/Security/User-has-left-the-company-now-getting-quot-Could-not-find-user/m-p/75983#M2524</link>
      <description>&lt;P&gt;Removing those entries in viewstates.conf doesn't resolve the error either.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Feb 2012 23:33:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/User-has-left-the-company-now-getting-quot-Could-not-find-user/m-p/75983#M2524</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2012-02-21T23:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: User has left the company, now getting "Could not find user:" errors</title>
      <link>https://community.splunk.com/t5/Security/User-has-left-the-company-now-getting-quot-Could-not-find-user/m-p/75984#M2525</link>
      <description>&lt;P&gt;Make sure the users not in any meta files either.  If you're on a linux machine I'd do the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;grep -r "username" $SPLUNK_HOME
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That'll find all instances of the user name in any configuration files.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2012 08:07:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/User-has-left-the-company-now-getting-quot-Could-not-find-user/m-p/75984#M2525</guid>
      <dc:creator>Brian_Osburn</dc:creator>
      <dc:date>2012-02-22T08:07:39Z</dc:date>
    </item>
  </channel>
</rss>

