<?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 Enterprise License update in Security</title>
    <link>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30493#M13743</link>
    <description>&lt;P&gt;We'v got license violations six times with 500MB license level, but when we update with new license level 20G(stop then start in CLI), it still does not work for searching. The license detail in splunk web has been reflashed by 20,480MB, but the old violation records remain existing, the web's title also shows "reached the maximun license violations for this time period". The new license date has not been expired.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Aug 2010 08:52:27 GMT</pubDate>
    <dc:creator>hjwang</dc:creator>
    <dc:date>2010-08-16T08:52:27Z</dc:date>
    <item>
      <title>Enterprise License update</title>
      <link>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30493#M13743</link>
      <description>&lt;P&gt;We'v got license violations six times with 500MB license level, but when we update with new license level 20G(stop then start in CLI), it still does not work for searching. The license detail in splunk web has been reflashed by 20,480MB, but the old violation records remain existing, the web's title also shows "reached the maximun license violations for this time period". The new license date has not been expired.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Aug 2010 08:52:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30493#M13743</guid>
      <dc:creator>hjwang</dc:creator>
      <dc:date>2010-08-16T08:52:27Z</dc:date>
    </item>
    <item>
      <title>Re: Enterprise License update</title>
      <link>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30494#M13744</link>
      <description>&lt;P&gt;You should contact support for license problems. They should be able to provide you with a reset key, although I had thought that application of a new license should &lt;EM&gt;also&lt;/EM&gt; reset the violations count to zero.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Aug 2010 10:26:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30494#M13744</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-08-16T10:26:41Z</dc:date>
    </item>
    <item>
      <title>Re: Enterprise License update</title>
      <link>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30495#M13745</link>
      <description>&lt;P&gt;Our supporter says it may be a license bug for version 4.1.4. After doing clean all -f command,it should work fine.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Aug 2010 10:18:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30495#M13745</guid>
      <dc:creator>hjwang</dc:creator>
      <dc:date>2010-08-17T10:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: Enterprise License update</title>
      <link>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30496#M13746</link>
      <description>&lt;P&gt;Did anyone find a resolution to this?  I just upgraded from 4.1.3 to 4.1.4 and am now receiving licensing errors whereas before I wasn't.  &lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2010 21:28:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30496#M13746</guid>
      <dc:creator>mmletzko</dc:creator>
      <dc:date>2010-09-17T21:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: Enterprise License update</title>
      <link>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30497#M13747</link>
      <description>&lt;P&gt;Looks like the upgrade to 4.1.4 may have just uncovered incorrect licensing in prior versions.  Before the upgrade from 4.1.3 to 4.1.4 we had 6 violations in the last 30 days, but no issues with using search - not messages about exceeding our license, except for the logged violations.&lt;/P&gt;

&lt;P&gt;After the upgrade, we got the licensing error and search was disabled.  After rolling back to 4.1.3, the error went away.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Sep 2010 03:40:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Enterprise-License-update/m-p/30497#M13747</guid>
      <dc:creator>mmletzko</dc:creator>
      <dc:date>2010-09-18T03:40:47Z</dc:date>
    </item>
  </channel>
</rss>

