<?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: Dev license receiving exceeded licence limit in Security</title>
    <link>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342916#M12534</link>
    <description>&lt;P&gt;ah, in the case of existing warnings/license violations,  try flipping the license group on the server to free, then install the new one, does that get you around it?&lt;/P&gt;

&lt;P&gt;Otherwise, I believe if you set up another instance of Splunk and install the license there, then point your instance as a slave at it, it may get you around it. &lt;/P&gt;</description>
    <pubDate>Sun, 11 Jun 2017 13:37:32 GMT</pubDate>
    <dc:creator>mattymo</dc:creator>
    <dc:date>2017-06-11T13:37:32Z</dc:date>
    <item>
      <title>Dev license receiving exceeded licence limit</title>
      <link>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342913#M12531</link>
      <description>&lt;P&gt;I recently renewed my Dev license and am now getting the following error when running searches&lt;/P&gt;

&lt;P&gt;Error in 'litsearch' command: Your Splunk license expired or you have exceeded your license limit too many times.&lt;/P&gt;

&lt;P&gt;Is there any way to reset the expiration?&lt;/P&gt;</description>
      <pubDate>Sat, 10 Jun 2017 02:46:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342913#M12531</guid>
      <dc:creator>memery_ing</dc:creator>
      <dc:date>2017-06-10T02:46:43Z</dc:date>
    </item>
    <item>
      <title>Re: Dev license receiving exceeded licence limit</title>
      <link>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342914#M12532</link>
      <description>&lt;P&gt;Do you still have the old license installed?&lt;/P&gt;

&lt;P&gt;If so remove the expired one and install the new one. &lt;/P&gt;

&lt;P&gt;I don't believe the Dev licenses are stackable, so the old one may be still in your way.&lt;/P&gt;

&lt;P&gt;Go to Settings &amp;gt; Licenses and remove the expired one.&lt;/P&gt;</description>
      <pubDate>Sat, 10 Jun 2017 23:37:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342914#M12532</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2017-06-10T23:37:31Z</dc:date>
    </item>
    <item>
      <title>Re: Dev license receiving exceeded licence limit</title>
      <link>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342915#M12533</link>
      <description>&lt;P&gt;Thanks for your reply&lt;/P&gt;

&lt;P&gt;The only license installed is the new one.&lt;/P&gt;

&lt;P&gt;I had numerous "This pool has exceeded its configured poolsize=0 bytes. A warning has been recorded for all members" alerts when the old license expired.  I am assuming this is what caused it.&lt;/P&gt;</description>
      <pubDate>Sun, 11 Jun 2017 00:20:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342915#M12533</guid>
      <dc:creator>memery_ing</dc:creator>
      <dc:date>2017-06-11T00:20:10Z</dc:date>
    </item>
    <item>
      <title>Re: Dev license receiving exceeded licence limit</title>
      <link>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342916#M12534</link>
      <description>&lt;P&gt;ah, in the case of existing warnings/license violations,  try flipping the license group on the server to free, then install the new one, does that get you around it?&lt;/P&gt;

&lt;P&gt;Otherwise, I believe if you set up another instance of Splunk and install the license there, then point your instance as a slave at it, it may get you around it. &lt;/P&gt;</description>
      <pubDate>Sun, 11 Jun 2017 13:37:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342916#M12534</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2017-06-11T13:37:32Z</dc:date>
    </item>
    <item>
      <title>Re: Dev license receiving exceeded licence limit</title>
      <link>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342917#M12535</link>
      <description>&lt;P&gt;Neither of those suggestion worked.&lt;/P&gt;

&lt;P&gt;But, the new instance does work with the Dev license, so I am migrating the data across to it, which is accessible.&lt;/P&gt;

&lt;P&gt;Thanks for your help&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2017 23:57:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Dev-license-receiving-exceeded-licence-limit/m-p/342917#M12535</guid>
      <dc:creator>memery_ing</dc:creator>
      <dc:date>2017-06-12T23:57:55Z</dc:date>
    </item>
  </channel>
</rss>

