<?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: After ITSI migration to 3.0, the services are empty, ERROR: Parameter &amp;quot;name&amp;quot; must be 100 characters or less in Splunk ITSI</title>
    <link>https://community.splunk.com/t5/Splunk-ITSI/After-ITSI-migration-to-3-0-the-services-are-empty-ERROR/m-p/334480#M406</link>
    <description>&lt;P&gt;We found that the long object was a Service KPI search, relying on a base search from the module DA-ITSI-ITSI-Health-Check-Module&lt;/P&gt;

&lt;P&gt;search : &lt;BR /&gt;
[DA-ITSI-ITSI-Health-Check-Module-DA-ITSI-ITSI-Health-Check-Module_ITSI-Health_Splunk.Searches]&lt;/P&gt;

&lt;P&gt;Saved Search Name that was too long : (128 chars &amp;gt; 100 char limit)&lt;BR /&gt;
Indicator - Shared - DA-ITSI-ITSI-Health-Check-Module-DA-ITSI-ITSI-Health-Check-Module_ITSI-Health_Splunk.Searches - ITSI Search&lt;/P&gt;

&lt;P&gt;The problem was that the objects in the kvstore was a combination of the service, indicator and base search name, and went over the limit.&lt;/P&gt;

&lt;P&gt;Solution : &lt;BR /&gt;
- once rolled back to 2.6.*&lt;BR /&gt;
- go to configuration &amp;gt; services , and find the service calling that base search, and delete it&lt;BR /&gt;
- stop splunk&lt;BR /&gt;
- redo the upgrade to 3.0&lt;BR /&gt;
- check the services after&lt;/P&gt;

&lt;P&gt;PS : As the app/module DA-ITSI-ITSI-Health-Check-Module has been deprecated, it's better to remove the module anyway.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 16:28:38 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2020-09-29T16:28:38Z</dc:date>
    <item>
      <title>After ITSI migration to 3.0, the services are empty, ERROR: Parameter "name" must be 100 characters or less</title>
      <link>https://community.splunk.com/t5/Splunk-ITSI/After-ITSI-migration-to-3-0-the-services-are-empty-ERROR/m-p/334479#M405</link>
      <description>&lt;P&gt;I did an upgrade of my ITSI to 3.0, and in the process I saw some errors in the itsi_migration.log&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;2017-10-23 09:53:36,941 INFO [itsi.migration] [base_migration_interface] [_get_object_file_list] [23596] obtain the local storage target file list: ['D:\\Splunk\\var\\itsi\\migration_helper\\kpi_base_search___0.json'] &lt;BR /&gt;
2017-10-23 09:53:41,783 ERROR [itsi.migration] [migration] [migration_bulk_save_to_kvstore] [23596] [HTTP 400] Bad Request; [{'type': 'ERROR', 'text': 'Parameter "name" must be 100 characters or less.', 'code': None}]&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Now the service panel does not load, and I had to rollback to ITSI 2.6.*&lt;/P&gt;</description>
      <pubDate>Wed, 25 Oct 2017 20:47:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-ITSI/After-ITSI-migration-to-3-0-the-services-are-empty-ERROR/m-p/334479#M405</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2017-10-25T20:47:31Z</dc:date>
    </item>
    <item>
      <title>Re: After ITSI migration to 3.0, the services are empty, ERROR: Parameter "name" must be 100 characters or less</title>
      <link>https://community.splunk.com/t5/Splunk-ITSI/After-ITSI-migration-to-3-0-the-services-are-empty-ERROR/m-p/334480#M406</link>
      <description>&lt;P&gt;We found that the long object was a Service KPI search, relying on a base search from the module DA-ITSI-ITSI-Health-Check-Module&lt;/P&gt;

&lt;P&gt;search : &lt;BR /&gt;
[DA-ITSI-ITSI-Health-Check-Module-DA-ITSI-ITSI-Health-Check-Module_ITSI-Health_Splunk.Searches]&lt;/P&gt;

&lt;P&gt;Saved Search Name that was too long : (128 chars &amp;gt; 100 char limit)&lt;BR /&gt;
Indicator - Shared - DA-ITSI-ITSI-Health-Check-Module-DA-ITSI-ITSI-Health-Check-Module_ITSI-Health_Splunk.Searches - ITSI Search&lt;/P&gt;

&lt;P&gt;The problem was that the objects in the kvstore was a combination of the service, indicator and base search name, and went over the limit.&lt;/P&gt;

&lt;P&gt;Solution : &lt;BR /&gt;
- once rolled back to 2.6.*&lt;BR /&gt;
- go to configuration &amp;gt; services , and find the service calling that base search, and delete it&lt;BR /&gt;
- stop splunk&lt;BR /&gt;
- redo the upgrade to 3.0&lt;BR /&gt;
- check the services after&lt;/P&gt;

&lt;P&gt;PS : As the app/module DA-ITSI-ITSI-Health-Check-Module has been deprecated, it's better to remove the module anyway.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 16:28:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-ITSI/After-ITSI-migration-to-3-0-the-services-are-empty-ERROR/m-p/334480#M406</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2020-09-29T16:28:38Z</dc:date>
    </item>
  </channel>
</rss>

